Bug#766727: tracker.debian.org: should link excuses for binNMUs too

[Samuel Thibault <sthibault@debian.org>]

Package: tracker.debian.org
Severity: normal

Hello,

I was wondering why the nvidia-cuda-toolkit transition wasn't
happening.  The QA page for nvidia-cuda-toolkit or one of its rev-dep,
starpu-contrib, would only show "Valid candidate".  It happens that it
doesn't migrate because the starpu-contrib rev-dep, already binNMUed, is
actually waiting for gcc-4.8 to migrate, and this issue doesn't shows up
on the QA page, only in the grep-excuses output:

starpu-contrib/i386 (1.1.3+dfsg-2 to 1.1.3+dfsg-2)
...
    Updated binary: libstarpu-contrib-1.1-7 (1.1.3+dfsg-2 to 1.1.3+dfsg-2+b1)
...
    Invalidated by dependency
    Not considered
    Depends: starpu-contrib/i386 gcc-4.8 (not considered)

Could QA be made to show this kind of excuse too?

Samuel

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.17.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- 
Samuel
quit   When the quit statement is read, the  bc  processor
       is  terminated, regardless of where the quit state-
       ment is found.  For example, "if  (0  ==  1)  quit"
       will cause bc to terminate.
(Seen in the manpage for "bc". Note the "if" statement's logic)