Your message dated Sun, 22 Jan 2017 17:19:05 +0100
with message-id <[email protected]>
and subject line Re: Bug#851772: nmu: madplay_0.15.2b-8.1
has caused the Debian Bug report #851772,
regarding nmu: madplay_0.15.2b-8.1
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 [email protected]
immediately.)
--
851772: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851772
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
nmu madplay_0.15.2b-8.1 . ANY . unstable . -m "Rebuild against libid3tag
0.15.1b-12"
adequate reports:
madplay: symbol-size-mismatch /usr/bin/madplay => id3_build
madplay was built against libid3tag 0.15.1b-11 (which was itself built
in 2014), while 0.15.1b-12 was built two years later with a newer
toolchain ...
Andreas
--- End Message ---
--- Begin Message ---
On Wed, Jan 18, 2017 at 17:38:14 +0100, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: binnmu
>
> nmu madplay_0.15.2b-8.1 . ANY . unstable . -m "Rebuild against libid3tag
> 0.15.1b-12"
>
> adequate reports:
>
> madplay: symbol-size-mismatch /usr/bin/madplay => id3_build
>
I don't know why adequate complains but that doesn't sound like it
requires a binNMU.
Cheers,
Julien
--- End Message ---
