Re: Bug#318463: Proposed update to e2fsprogs for stable

[Theodore Ts'o <tytso@mit.edu>]

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?

Many thanks,

						- Ted