Bug#930433: bugs.debian.org: source for libasan5 is gcc-8, not gcc-9

2019-06-12 Thread Don Armstrong
On Thu, 13 Jun 2019, Vincent Lefevre wrote:
> The "src:gcc-9" is incorrect, as the source for libasan5 is gcc-8
> (at least for the reported version), not gcc-9. The bug should
> appear on
> 
>   https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gcc-8
> 
> not on
> 
>   https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gcc-9

The source for libasan5 is gcc-8 and gcc-9. In reality, it should show
up on both, but we currently do source mapping using the information in
unstable, not the information in testing or stable. [And ideally, it
should tell you that the bug is found in gcc-8, but in some other branch
for gcc-9.]

In my current development branch I have addressed this, but this is
significantly more complicated to get right in all of the edge cases,
which is why it won't be fixed before I roll out all of those other
changes.


-- 
Don Armstrong  https://www.donarmstrong.com

This can't be happening to me. I've got tenure.
 -- James Hynes _Publish and Perish_



Bug#930433: bugs.debian.org: source for libasan5 is gcc-8, not gcc-9

2019-06-12 Thread Vincent Lefevre
On 2019-06-12 17:23:31 +0200, Ivo De Decker wrote:
> Hi,
> 
> On Thu, Jun 13, 2019 at 12:13:30AM +0900, Vincent Lefevre wrote:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930430 contains:
> > 
> > "Package: libasan5; Maintainer for libasan5 is Debian GCC Maintainers
> > ; Source for libasan5 is src:gcc-9 (PTS,
> > buildd, popcon).
> > [...]
> > Found in version gcc-8/8.3.0-7"
> > 
> > The "src:gcc-9" is incorrect, as the source for libasan5 is gcc-8
> > (at least for the reported version), not gcc-9. The bug should
> > appear on
> > 
> >   https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gcc-8
> > 
> > not on
> > 
> >   https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gcc-9
> 
> The BTS looks at the newest know version to decide the source <-> binary
> mapping. If the mapping is different in unstable and experimental, the one
> from experimental will be used (because the version is higher). That's what's
> happening here (libasan5 is built by gcc-9 in experimental).
> 
> It might be better to prefer the mapping from unstable over the one
> from experimental, even though that will be wrong in some other
> cases. I don't know if it's realistic to have the mapping depend on
> the version information in the bug.

Perhaps it should use the latest version *and* add any source from
the "found" field. This should affect the page of the bug and the
one for any such source, e.g.

  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gcc-8

This will be useful even when unstable gets the new version.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#930433: bugs.debian.org: source for libasan5 is gcc-8, not gcc-9

2019-06-12 Thread Ivo De Decker
Hi,

On Thu, Jun 13, 2019 at 12:13:30AM +0900, Vincent Lefevre wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930430 contains:
> 
> "Package: libasan5; Maintainer for libasan5 is Debian GCC Maintainers
> ; Source for libasan5 is src:gcc-9 (PTS,
> buildd, popcon).
> [...]
> Found in version gcc-8/8.3.0-7"
> 
> The "src:gcc-9" is incorrect, as the source for libasan5 is gcc-8
> (at least for the reported version), not gcc-9. The bug should
> appear on
> 
>   https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gcc-8
> 
> not on
> 
>   https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gcc-9

The BTS looks at the newest know version to decide the source <-> binary
mapping. If the mapping is different in unstable and experimental, the one
from experimental will be used (because the version is higher). That's what's
happening here (libasan5 is built by gcc-9 in experimental).

It might be better to prefer the mapping from unstable over the one from
experimental, even though that will be wrong in some other cases. I don't know
if it's realistic to have the mapping depend on the version information in the
bug.

Ivo



Bug#930433: bugs.debian.org: source for libasan5 is gcc-8, not gcc-9

2019-06-12 Thread Vincent Lefevre
Package: bugs.debian.org
Severity: normal

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930430 contains:

"Package: libasan5; Maintainer for libasan5 is Debian GCC Maintainers
; Source for libasan5 is src:gcc-9 (PTS,
buildd, popcon).
[...]
Found in version gcc-8/8.3.0-7"

The "src:gcc-9" is incorrect, as the source for libasan5 is gcc-8
(at least for the reported version), not gcc-9. The bug should
appear on

  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gcc-8

not on

  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gcc-9

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled