Your message dated Fri, 12 Feb 2016 18:29:53 +0100
with message-id <[email protected]>
and subject line Re: Bug#814470: nmu: shibboleth-resolver_1.0.0-1
has caused the Debian Bug report #814470,
regarding nmu: shibboleth-resolver_1.0.0-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.)
--
814470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814470
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
nmu shibboleth-resolver_1.0.0-1 . ANY . unstable . -m "Rebuild against the
libstdc++ v5 transitioned shibboleth stack."
This doesn't seem to export any symbols affected by the libstdc++ v5
transition (but it needs several of them), so a binNMU should be
sufficient in this case, no rename required.
Andreas
--- End Message ---
--- Begin Message ---
On 12/02/16 00:01, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: binnmu
>
> nmu shibboleth-resolver_1.0.0-1 . ANY . unstable . -m "Rebuild against the
> libstdc++ v5 transitioned shibboleth stack."
>
> This doesn't seem to export any symbols affected by the libstdc++ v5
> transition (but it needs several of them), so a binNMU should be
> sufficient in this case, no rename required.
Scheduled.
Cheers,
Emilio
--- End Message ---
