On Tue, 2016-12-27 at 16:13 -0500, Theodore Ts'o wrote:
> On Tue, Dec 27, 2016 at 07:56:36PM +0000, Adam D. Barratt wrote:
> > Thankfully none of that worked. I say thankfully, because you'd have
> > given release.d.o an allegedly RC bug (it may be RC for e2fsprogs, it's
> > certainly not so for release.d.o) and removed the original bug from
> > where it belongs. (The binNMU doesn't resolve the fact that the original
> > issue existed - and for some versions still exists - in e2fsprogs.)
> 
> It only exists in the versions of e2fsprogs shipping in Jessie and
> before.  So unless the SRM's think that it's worth it to fix this
> issue via a change to e2fsprogs going to proposed-updates for Jessie
> (I'm not entirely convinced but if you want me to add the Built-Using
> and ask for a update to Jessie stable, I can do that, and we can punt
> on the binNMU for e2fsck-static since it will be obsoleted by the fix
> of e2fsprogs in Debian stable.)

I already scheduled the binNMUs for the handful of architectures that I
could, in the cloned #849488. You may wish to check the architecture
list there and confirm whether any of the others were typoes or if the
three architectures mentioned are sufficient.

Regards,

Adam

Reply via email to