Hi, On 6/7/24 22:40, Alexandre Detiste wrote:
Maybe a compromise would be to at least mandate some UTF-8 locale.
Having an UTF-8 locale available would be a good thing, but allowing packages to rely on the active locale to be UTF-8 based reduces our testing scope.
Basically, we need to define the severity of locale bugs -- if we define that package builds can expect LC_ALL=C.UTF-8, and reproducible-builds testing finds out that passing a non-UTF-8 locale in causes a deviation or a build failure, is the maintainer free to close this "wontfix", or should this still be addressed?
Besides locales, there are other things that might affect outcomes, and we need to find some reasonable position between "packages should be reproducible even if built from the maintainer's user account on their personal machine" and "anything that is not a sterile systemd-nspawn container with exactly the requested Build-Depends and no Recommended packages causes undefined behaviour."
Personally my preference would be as close as possible to the former, because if I ever need to work on someone else's package, the chance is high that I will need incremental builds and a graphical debugger, and both of these are a major hassle in containers.
Simon
OpenPGP_0xEBF67A846AABE354.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
