On Thursday, October 2, 2025 12:08:28 AM Mountain Standard Time Holger Levsen wrote: > On Wed, Oct 01, 2025 at 04:20:16PM -0700, Soren Stoutner wrote: > > I maintain pyinstaller-hooks-contrib, which includes a test (run during > > build > > and in autopkgtests) that parses the system timezone. This test currently > > fails Salsa CI reprotest and other reproducibility tests because they modify > > the timezone in the build environment using syntax like GMT+12 instead of > > the > > Continent/City syntax. > > I think you have several options here: > > a.) set the timezone in the test (not 100% you can do this) > b.) disable the test > c.) disable Salsi CI reprotest and d.) > d.) do not care about tests.reproducible-builds.org/debian result, esp > if it reproduces on > https://reproduce.debian.net/all/unstable.html#pyinstaller-hooks-contrib > which it does. Yes, I can either disable the tests or ignore the results. Neither is my preferred option because the tests might catch some actual problem in the future that I would then miss. This is why I asked the question about whether using the GMT+12 syntax catches some actual problem that using Continent/City (this is the currently recommended way to set timezones in Linux) does not. If using GMT+12 is important for reproducibility tests, then I will simply disable these tests in my package. But if it isn’t, then my recommendation would be that Salsa CI and reproducible builds infrastructure and any other part of Debian using the GMT+12 syntax be changed to use Continent/City. -- Soren Stoutner soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.