> > 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. > > There is nothing that ensures that packages are built at the same time.
The testing scripts ensure that all packages migrate to testing at the same time. This is by design. What you are basically asking me is that I care about unstable as if it were stable (your mention of CVE issues suggests so, but neither unstable or testing shortly after a stable release are supposed to have real security support). That's not how we do things in Debian. Unstable is where we try new things even if they break other things. When other things break we fix the other things and move forward. Currently, I see that glibc FTBFS in testing as well: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/glibc.html but we don't have the new gettext in testing yet, so this temporary breakage of glibc in unstable does not really make things worse than they are, since we already have a FTBFS in testing for unrelated reasons. To summarize: Unstable is unstable. OTOH, I would consider reverting the commit if we discovered more bugs like #872869 (please take a look at that one), but you will notice that the gettext upstream maintainers have been extremely quick to provide a fix. Thanks.
