Hello release team,

There are new versions of the entire Shibboleth stack and dependency
libraries available, and I'm starting to look at packaging them.  Due to
upstream SONAME changes, I expect this to require a transition that will
entangle all of the following source packages:

    xml-security-c
    xmltooling
    opensaml
    opensaml2
    shibboleth-sp
    shibboleth-sp2

(opensaml and shibboleth-sp should probably be dropped from the archive
before the squeeze release, but I'm noto quite ready to do that yet.)

How would you like to handle the scheduling?  Should I hold off from
starting this right now due to pending transitions?  I know we have
several big ones in flight right now.

-- 
Russ Allbery ([email protected])               <http://www.eyrie.org/~eagle/>


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to