Package: release.debian.org
Followup-For: Bug #1099646

I would like advice about a test that I broke during this transition.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100373
We have ignored it as a reproducibility issue, but another symptom is
that gprbuild recompiles generated Ada sources and their reverse
dependencies again and again during package builds (at least during
the build, test and install steps).
On buildds, this only wastes resources, but this is confusing for
humans, and hard to connect with #1100373 (for example, 'debian/rules
dh_auto_build' and 'debian/rules build' behave differently because the
environment differs).
The fix is trivial
https://salsa.debian.org/debian/gprbuild/-/commit/2f1ecf1082709d6fd8a53d497d93b7739ca43176
but four reverse dependencies need a bin-NMU.

package              build-depends on      builds
----------------------------------------------------------------
gprbuild                                   libgnatprj-dev
alire                libgnatprj-dev
libgnatcoll          libgnatprj-dev        libgnatcoll-dev
libgnatcoll-bindings libgnatcoll-dev       libgnatcoll-iconv-dev
libgnatcoll-db       libgnatcoll-iconv-dev

libgnatcoll-iconv-dev does not call libgnatprj, but depends on the
virtual libgnatcoll-dev-HASH.  HASH will change.

nmu alire_1.2.1-2                 . ANY . -m 'Rebuild with SOURCE_DATE_EPOCH 
fixed in libgnatprj-dev'
dw  alire_1.2.1-2                 . ANY . -m 'libgnatprj-dev (>= 2025.0.0-4)'
nmu libgnatcoll_24.1.20230921-6   . ANY . -m 'Rebuild with SOURCE_DATE_EPOCH 
fixed in libgnatprj-dev'
dw  libgnatcoll_24.1.20230921-6   . ANY . -m 'libgnatprj-dev (>= 2025.0.0-4)'
nmu libgnatcoll-bindings_25.0.0-2 . ANY . -m 'Rebuild with SOURCE_DATE_EPOCH 
fixed in libgnatprj-dev'
dw  libgnatcoll-bindings_25.0.0-2 . ANY . -m 'libgnatcoll-dev (>= 
24.1.20230921-6+b1)'
nmu libgnatcoll-db_25.0.0-2       . ANY . -m 'Rebuild with SOURCE_DATE_EPOCH 
fixed in libgnatprj-dev'
dw  libgnatcoll-db_25.0.0-2       . ANY . -m 'libgnatcoll-iconv-dev (>= 
25.0.0-2+b1)'

Should I upload gprbuild despite the freeze, or wait for first dot
release?  In the first case, should I wait after this bug is closed
and open a distinct one? do an intermediate upload to experimental?

Reply via email to