Your message dated Fri, 7 Nov 2025 18:56:20 +0000
with message-id <[email protected]>
and subject line reproduce.debian.net is doing this, thus closing
has caused the Debian Bug report #888099,
regarding reproducible: Please consider doing separate arch/indep builds in
build2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
888099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888099
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: jenkins.debian.org
Severity: wishlist
When Debian developers follow best practices (source-only uploads), the
production Debian buildd infrastructure builds architecture-specific
packages and architecture-independent packages in two separate sbuild
invocations (dpkg-buildpackage -B, dpkg-buildpackage -A). This is not
particularly efficient (upstream source code normally ends up being
built twice), but amd64 buildd time is cheap.
However, reproducible-builds currently builds both sorts of package
together (dpkg-buildpackage -b). This can result in different bugs being
visible, for instance #887664 and which can be reproduced with -b but not
with -A or -B. I could also imagine it producing different built results.
For packages that build both Architecture: all and Architecture: any
(or packages of a specific architecture), it would be interesting for
"build2" to do two separate builds like the production buildd/sbuild
infrastructure does, then glue them together with mergechanges. This
would usually result in different .changes and .buildinfo files (which
should be treated as not a reproducibility failure, because the .changes
file is not consumed by end-users anyway) but would hopefully produce
identical binary packages.
smcv
--- End Message ---
--- Begin Message ---
hi,
I'm closing this bugreport, because reproduce.debian.net is doing this now:
architecture independent packages are built on https://reproduce.debian.net/all
while architecture dependent packages are built on
https://reproduce.debian.net/amd64 and https://reproduce.debian.net/arm64
and so on, just like the official buildds do.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
„Ich dachte immer, jeder sei gegen den Krieg, bis ich herausfand, dass es
welche gibt, die nicht hingehen müssen.“ (Erich Maria Remarque)
signature.asc
Description: PGP signature
--- End Message ---
