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
On 2023-02-28 22:18:14 +0100, Sebastian Ramacher wrote: > Control: clone -1 -2 > Control: reassign -2 gcc-11-cross-mipsen 5+c3 > Control: retitle -2 gcc-11-cross-mipsen: not binNMU-safe > > On 2023-02-28 22:13:59 +0100, Sebastian Ramacher wrote: > > 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. > > gcc-11-cross-mipsen is affected by the same issue. Cloning and > reassigning. … and there are more. Cheers -- Sebastian Ramacher
