Your message dated Wed, 21 Sep 2016 15:12:12 +0200
with message-id <>
and subject line Re: Bug#836370: transition: shibboleth
has caused the Debian Bug report #836370,
regarding transition: shibboleth
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

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Severity: normal
Usertags: transition

xmltooling 1.6, opensaml2 2.6 and shibboleth-sp2 2.6 each change their SONAME
in this new version of this software stack.  The new stack is already in
experimental, and the two external depending packages (shibboleth-resolver
and moonshot-gss-eap) build successfully against the new stack without any
source change.  The auto-xmltooling, auto-opensaml2 and auto-shibboleth-sp2
trackers look good, but here's a unified ben file:

title = "shibboleth";
is_affected = .depends ~ "libxmltooling6v5" | .depends ~ "libsaml8v5" | 
.depends ~ "libshibsp6v5" | .depends ~ "libxmltooling7" | .depends ~ "libsaml9" 
| .depends ~ "libshibsp7";
is_good = .depends ~ "libxmltooling7" | .depends ~ "libsaml9" | .depends ~ 
is_bad = .depends ~ "libxmltooling6v5" | .depends ~ "libsaml8v5" | .depends ~ 

These packages will also be part of the openssl transition, but they are
incompatible with OpenSSL-1.1.  Upstream is already working on that on a
separate branch.  This internal SONAME transition, on the other hand, is
very self-contained and should finish before that in my opinion.

--- End Message ---
--- Begin Message ---
All packages migrated to stretch, let's close this.

--- End Message ---

Reply via email to