hi Thorsten, On Sat, Sep 12, 2026 at 06:39:18AM +0200, Thorsten Glaser wrote: > I’ve recently found out that reproducible-builds nowadays fails > packages which produce different output when 'nocheck' is set vs. > unset.
just to be clear, are you talking about https://reproduce.debian.net/ or https://tests.reproducible-builds.org/debian/ ? (the diff is explained on top of https://reproduce.debian.net/) > This is wrong. > > If (if!) a 'nocheck' build *profile* is supported by the package, > then, if that build *profile* is set, the binary packages may not > differ. > > But the 'nocheck' build option *is* allowed to have binary > differences, and this is something important for various corner > cases. i'm not sure you are correct here (you might well be!), so i'm wondering: where is this documented? > So, please add it to DEB_BUILD_OPTIONS on either no or all builds, > and investigate into setting the 'nocheck' build *profile* on only > one build *iff* the package supports it. I’m not exactly sure how > to actually test for that, but if it only gets added to the variable > DEB_BUILD_PROFILES but not DEB_BUILD_OPTIONS, then it can just be > ignored by packages not supporting the 'nocheck' *profile*. ack. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ The era of global warming has ended, the era of global boiling has arrived. The heat is unbearable, and the level of fossil fuel profits & climate inaction is unacceptable. Humanity has unleashed destruction. This must not inspire despair, but action." — UNSG @AntonioGuterres
signature.asc
Description: PGP signature
