On Mon, Aug 21, 2017 at 09:51:36PM +0200, Helmut Grohne wrote: > Package: gettext > Version: 0.19.8.1-3 > Severity: serious > Justification: glibc ftbfs > User: helm...@debian.org > Usertags: rebootstrap > > The removal of POT-Creation-Date (#792687) is a nice thing to do, but > the archive isn't quite ready for it. > > * glibc FTBFS https://sourceware.org/bugzilla/show_bug.cgi?id=21508 and > no patch is available as of this writing.
That's a bug in an upstream bug tracker. Does our glibc also FTBFS for the same reason? Where is the Debian bug number? The way I read the upstream bug report: "tst-gettext fails", it does not seem the kind of bug which is difficult to fix. > * The commit changes .mo files and thus breaks M-A:sameness allover the > archive, e.g. #872806. Likely all packages shipping .mo files in > M-A:same packages are affected. The multiarch database on delfin.d.o > gives a clue: The commit does not really change any existing .mo file in the archive. It just makes the .mo files to be different when you rebuild the package. But in general this is supposed to happen at the same time in all architectures, triggered by a new Debian revision. Moreover: How many of those in the list do not also violate Debian policy section 8.2? Also, bug #872806 does not seem a good example to me, because the library should not contain unversioned .mo files to begin with. So, if I have to revert, I will do, but so far I don't see this is a catastrophic failure that requires a reversion. Thanks.
