Hi, On Thu, Jun 06, 2024 at 11:32:33AM +0200, Simon Richter wrote: > If your package is not reproducible without it, then your package is > broken. It can go in with the workaround, but the underlying problem > should be fixed at some point.
It's easy to say "should be fixed" but finding the source of such build problems is another matter. I was debugging a hard to find locale repro bug with some people at mDebConf Berlin and we had this thought: why don't we have a debugger for this yet? Seems pretty simple to detect in principle: At build-time, if a program doesn't call setlocale before using locale dependent standard library functions it's probably a reproducibility hazard. Using the LD_PRELOAD hack like fakeroot/faketime we could make the program crash or print a stack trace at the point it's trying to use the locale from the environment. That should make it easier to figure out where these problems even are. I wonder if there's other repro things we could screen for in a similar manner? --Daniel
signature.asc
Description: PGP signature
