Bug#683342: unblock: e2fsprogs/1.42.5-1

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

On Tue, Jul 31, 2012 at 10:28:54AM +0200, Niels Thykier wrote:
> Also (in answer to your other email), I believe it is fine with
> requesting them already now so we are aware of them.  :)

Since udeb's have been held, I guess this point is moot in any case.  :-)

Just for the record, none of these changes should be user visible from
a d-i perspective, although of course any change has testing
impliciations.

> Anyhow, I gave it a short look and...
>  * All debian patches appear to have been removed.  By the looks they
>    were fetched from upstream so I guess they were backports that are
>    no longer needed?  (I am asking because there is no mention of them
>    in d/changelog as far as I can tell)

Well, technically speaking they came from upstream first (e2fsprogs
gets developed with an upstream-first policy), and then I pull them
into debian/patches when I make interim releases of the debian package
between upstream releases.  So yes, all of these commits are reflected
upstream.

(Each of the "debian patches" references the upstream commit id's for
easier tracking, BTW.)

>  * Did you intend to include tune2fs.8.in.bak e2fsck.8.in.bak?

Argh, no, I didn't.  Thanks for pointing that out.  Unfortunately,
it's in the upstream release tarball which has already been published
and GPG signed, so it's too late to fix this now.

My script for generating the release tarball needs some tweaking so
that these files (left over from a patch application) get filtered out
automatically.  I have a .gitignore entry which is why I didn't notice
them, sigh.

					- Ted