#1032165 gcc-12-cross-ports: not binNMU safe

Package:
src:gcc-12-cross-ports
Source:
src:gcc-12-cross-ports
Submitter:
Sebastian Ramacher
Date:
2023-06-18 08:21:02 UTC
Severity:
normal
#1032165#5
Date:
2023-02-28 21:13:59 UTC
From:
To:
Source: gcc-12-cross-ports
Version: 12
Severity: serious

The method to compute the version of the binary packages is not
binNMU-safe. This can be seen from the latest round of binNMUs to
rebuild for outdated Built-Using fields. See
https://buildd.debian.org/status/fetch.php?pkg=gcc-12-cross-ports&arch=amd64&ver=12%2Bb1&stamp=1677602107&raw=0

As it can be seen from the log, the version computed for the binary
packages is the same as the one of the build of the initial upload of
version 12. The binNMU version -- b1 in this case -- is missing.

Cheers
#1032165#10
Date:
2023-02-28 21:18:14 UTC
From:
To:
Control: clone -1 -2
Control: reassign -2 gcc-11-cross-mipsen 5+c3
Control: retitle -2 gcc-11-cross-mipsen: not binNMU-safe

gcc-11-cross-mipsen is affected by the same issue. Cloning and
reassigning.

Cheers
#1032165#17
Date:
2023-03-01 18:38:46 UTC
From:
To:
Control: clone -1 -2 -3 -4
Control: reassign -2 gcc-9-cross-ports 25
Control: retitle -2 gcc-9-cross-ports: not binNMU-safe
Control: reassign -3 gcc-9-cross 27
Control: retitle -3 gcc-9-cross: not binNMU-safe
Control: reassign -4 gcc-10-cross-mipsen 3+c5
Control: retitle -4 gcc-10-cross-mipsen: not binNMU-safe

… and there are more.

Cheers
#1032165#24
Date:
2023-06-18 08:17:10 UTC
From:
To:
updating the Built-Using tag almost always means, that you build against a new
compiler version, also most likely modifying all the target binaries
(lib*-cross-*), which are packaged as binary-independent packages. So a binNMU
just doesn't make sense for the -cross packages.

Efforts to improve the situation should go into getting rid off these packages,
however this requires britney support for dependencies on foreign architectures
and support of the testing pocket for the so called ports architectures.