[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#710329: marked as done (transition: libxml-security-c17)

Your message dated Thu, 01 Aug 2013 23:17:54 +0100
with message-id <1375395474.25765.20.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#710329: transition: libxml-security-c17
has caused the Debian Bug report #710329,
regarding transition: libxml-security-c17
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 owner@bugs.debian.org
immediately.)


-- 
710329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710329
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Hello folks,

I'm preparing a new version of the Shibboleth packages, which as usual
involves three library transitions, although they're all used only by
this package set.  libxml-security-c is the lowest-level, but this also
involves libxmltooling (5 -> 6) and libsaml (7 -> 8).

These versions are required for the new upstream version of the
shibboleth-sp2 source package, which in turn is required for Apache 2.4
support, so from that you can see why I'm working on this now.  :)

Unfortunately, and this is the part about which I wanted to give you
advance warning, the new versions of these packages add a dependency
on Boost.  I'm therefore worried that, as well as being its own
mini-transition, I may end up entangling the Apache transition with the
Boost transition if I just push this stuff to unstable.

I'm staging the packages in experimental and have everything done except
for the actual shibboleth-sp2 package and its Apache module, which I'm
going to work on tomorrow.  But I will hold off on uploading this package
set to unstable (that is xml-security-c, xmltooling, opensaml2, and
shibboleth-sp2 as source packages) until I hear from you about how you
want to time this with everything else.

Ben file:

title = "libxml-security-c17";
is_affected = .depends ~ "libxml-security-c16" | .depends ~ "libxml-security-c17";
is_good = .depends ~ "libxml-security-c17";
is_bad = .depends ~ "libxml-security-c16";


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.8-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
On Tue, 2013-07-09 at 14:25 -0700, Russ Allbery wrote:
> Julien Cristau <jcristau@debian.org> writes:
> > On Wed, May 29, 2013 at 16:48:19 -0700, Russ Allbery wrote:
> 
> >> I'm staging the packages in experimental and have everything done
> >> except for the actual shibboleth-sp2 package and its Apache module,
> >> which I'm going to work on tomorrow.  But I will hold off on uploading
> >> this package set to unstable (that is xml-security-c, xmltooling,
> >> opensaml2, and shibboleth-sp2 as source packages) until I hear from you
> >> about how you want to time this with everything else.
> 
> > As this is needed for apache 2.4, feel free to go ahead.
> 
> Excellent, thanks!  I'll start this week.

Apache 2.4 migrated during this evening's britney run, allowing her to
remove libsaml7, libxml-security-c16 and libxmltooling5. Looks like this
is all done; closing.

Regards,

Adam

--- End Message ---
Reply to: