[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#991049: marked as done (gcc-10-cross-mipsen: Incorrect Source: version generated for binary packages in binNMUs)



Your message dated Tue, 13 Jul 2021 17:01:28 +0200
with message-id <[🔎] 9c7747e5-2a0b-4141-cf61-3ff0c9b5233e@debian.org>
and subject line Re: Incorrect Source: version generated for binary packages in binNMUs
has caused the Debian Bug report #991049,
regarding gcc-10-cross-mipsen: Incorrect Source: version generated for binary packages in binNMUs
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 owner@bugs.debian.org
immediately.)


-- 
991049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991049
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-9-cross
Version: 25
Severity: serious
Tags: ftbfs
Control: clone -1 -2 -3 -4
Control: reassign -2 gcc-9-cross-ports 23
Control: retitle -2 gcc-9-cross-ports: Incorrect Source: version generated for binary packages in binNMUs
Control: reassign -3 gcc-10-cross 15
Control: retitle -3 gcc-10-cross: Incorrect Source: version generated for binary packages in binNMUs
Control: reassign -4 gcc-10-cross-ports 16
Control: retitle -4 gcc-10-cross-ports: Incorrect Source: version generated for binary packages in binNMUs

https://buildd.debian.org/status/package.php?p=gcc-9-cross&suite=sid
https://buildd.debian.org/status/package.php?p=gcc-9-cross-ports&suite=sid
https://buildd.debian.org/status/package.php?p=gcc-10-cross-ports&suite=sid

...
 Package: cpp-9-aarch64-linux-gnu
 Source: gcc-9-cross (26+b1)
 Version: 9.4.0-1cross2
 Architecture: amd64
...

--- End Message ---
--- Begin Message ---
sorry, but these are bogus reports.  There's no requirement that a package has
to be binNMUable.  And for the GCC cross packages it's plainly wrong. Just
building the compilers, and not the runtime libraries lets these diverge, ending
up with a mix of packages built from two different compiler versions.

--- End Message ---

Reply to: