Control: severity -1 important
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
Processing control commands:
> clone -1 -2 -3 -4
Bug #1032165 [src:gcc-12-cross-ports] gcc-12-cross-ports: not binNMU safe
Bug 1032165 cloned as bugs 1032216-1032218
> reassign -2 gcc-9-cross-ports 25
Bug #1032216 [src:gcc-12-cross-ports] gcc-12-cross-ports: not binNMU safe
Bug reassigne
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:
Processing control commands:
> clone -1 -2
Bug #1032165 [src:gcc-12-cross-ports] gcc-12-cross-ports: not binNMU safe
Bug 1032165 cloned as bug 1032167
> reassign -2 gcc-11-cross-mipsen 5+c3
Bug #1032167 [src:gcc-12-cross-ports] gcc-12-cross-ports: not binNMU safe
Bug reassigned from p
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
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
6 matches
Mail list logo
