On Sun, 2014-11-02 at 13:08 -0500, Michael Gilbert wrote: > On Sun, Nov 2, 2014 at 12:53 PM, Andreas Beckmann wrote: > > Please prepare an update for wheezy and follow the > > stable-proposed-updates procedure (file a PU request against > > release.debian.org including a source debdiff). > > Wait, sid and wheezy have the same version, so we need to be a bit more > > careful. > > First upload it to sid (make no other changes than the Breaks/Replaces, > > we need to get this into jessie and wheezy), using version 3.0.1-2. > > Prepare a rebuild for wheezy, version it 3.0.1-2~deb7u1. > > File a PU request for wheezy. > > File an UNBLOCK request for jessie, this must have happened before the > > freeze (Nov 5)! > > The upload to unstable is not necessary. Once the pu is accepted into > wheezy proper, jessie and sid will also be updated to the exact same > version automatically to avoid that problem. > > Long story short, only the wheezy pu is necessary.
That might be true if the fix could wait until the next stable point release (unplanned yet, but at the earliest in mid-December). Aside from anything else, at least this SRM will be following standard procedure and not acking the wheezy fix until at least unstable is fixed in any case. The propagation of packages from stable to testing and unstable during a point release to avoid breaking the archive constraints is mostly used for packages which were updated via the security archive but have not yet been fixed in unstable, or for the small number of packages such as debian-installer where development is often minimal in unstable during much of the release cycle. It is certainly not intended as a means of avoiding fixing RC bugs in unstable / testing, particularly during a freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
