Re: Bug#847575: closed by Hilko Bengen <bengen@debian.org> (no embedded dietlibc)
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.)
Otherwise, I plan to close the e2fsprogs bugs since it's fixed in
Debian Stretch, and with the decision not to try to address this in
Jessie, a "wontfix" for older versions of e2fsprogs.
Apologies for not adjusting the priority as part of my attempt to move
this bug to release.debian.org, but the theory was that fixing this
via a binNMU of e2fsck-static was sufficient, given how late we are in
Jessie's life cycle, and it wasn't worth trying to fix this bug in
stable. If I'm wrong in this, and the SRM's would support/prefer to
fix this via an update to e2fsprogs in Jessie and spinning new binary
debs for all architectures, I'll stand corrected and we can go down
that route.
Cheers,
- Ted
Reply to: