On Mon, Aug 22, 2005 at 08:17:26PM -0400, Theodore Ts'o wrote: > On Mon, Aug 22, 2005 at 05:24:25PM -0400, Theodore Ts'o wrote: > > Thanks! I've just uploaded e2fsprogs_1.37-2sarge2. > Oops. It was rejected due to e2fsprogs_1.37-2sarge2 being newer than > what's in testing. > This is apparently because e2fsprogs has been frozen, so newer > versions have not been moved from unstable to testing; so testing is > still at e2fsprogs_1.37-2sarge1. > If it had not been frozen, 1.38-1 would have moved to testing already, > and while there is (now) a grave bug filed against 1.38-1, it is also > in 1.37-2sarge1, and I have just uploaded 1.38-2 which also addresses > the bug. > Is there a reason why unstable->testing transitions for e2fsprogs > should still be frozen at this point? During the sarge cycle, we were bitten on a number of occasions by letting in source packages that build udebs without syncing the udebs at the same time. The "freeze" of these packages is for this reason only; any time you need an update of e2fsprogs to be let in, please just ask. Unfortunately, aside from being too fresh to be pushed in, 1.38-2 is now also blocked (like everything else) by glibc, so this version won't be reaching testing for at least a couple of weeks. I don't know how that interacts with Joey's schedule for 3.1r1. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature