On Wed, 04 Sep 2019 at 12:18:44 +0100, Ian Jackson wrote:
> Simon McVittie writes ("Re: Bug#939280: dgit push-source rejects source-only
> .changes containing .orig.tar.gz.asc"):
> > for example during the buster
> > development cycle, sbuild from unstable would have done builds with
> > LC_ALL=C.UTF-8, but the production buildds used LC_ALL=POSIX, which
> > makes some of my packages fail build-time tests because they want to
> > print strings that are not representable in ASCII
>
> Glerk. We should probably change the buildd locale...
sbuild in buster uses LC_ALL=C.UTF-8, which I think is correct; but the
sbuild in buster probably has other bugs or bits of non-ideal behaviour
that will only be fixed in bullseye, and will need to be worked around in
the packages that they affect (with missing workarounds being de facto
RC bugs) for as long as buildds are still running sbuild on buster. And
so on for subsequent releases.
(#898949 in schroot is the best example I can think of right now for a
bug in buster's sbuild stack.)
smcv
