Re: Bug#24513: mixed dependency: wm2 depends on libc6 and xlib6
> Odd. Why didn't the bug-fixing wm2_3-3 go into frozen? Should I ask
> to have wm2_4-1 moved into frozen now? Or should I rebuild a package
> for version 3? Or should I reupload the deb, dsc, and diff for the NMU
> wm2_3-3? I'm partial to moving the version from slink, as it /does/
> fix the bug, and there aren't any new features in wm2 version 4.
changelog of wm2 says:
> wm2 (3-3) unstable; urgency=low
which means wm2_3-3 will go into unstable (mapped to slink) only. If
the package should go into frozen (mapped to hamm) as well as
unstable, it should be:
> wm2 (3-3) frozen unstable; urgency=low
Since hamm is already frozen, you cannot ask ftp manager to move the
new upstream version of wm2_4-1 into hamm (frozen allows you to upload
bug-fix-only packages), so you'll have to build wm2_3-4 with:
> wm2 (3-4) frozen; urgency=low
Generally,
1. If there's no new upstream version in unstable, bug-fix-only
version should go into frozen and unstable.
2. If there's a new upstream version in unstable, bug-fix-only version
should go into frozen only.
3. Needless to say, new upstream version should go into unstable only.
----
Keita Maehara <maehara@debian.or.jp>
PGP Key fingerprint = 82 37 2F 1E 06 ED C4 37 1E E2 C2 96 22 B8 B3 F1
--
To UNSUBSCRIBE, email to debian-mentors-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: