Shibboleth2 packaging

Ferenc Wagner wferi at
Tue May 13 15:50:24 UTC 2008

Russ Allbery <rra at> writes:

> Ferenc Wagner <wferi at> writes:
>> OK, thanks.  I'll revert it, but have to leave now.
>> Russ, I'm otherwise done with xmltooling and opensaml2.  Please tell
>> me what else has to be done before the first upload.
> Will do.  xalan was just fixed, so I need to do the 1.3 stack uploads, and
> then looking at the 2.0 stack is my next priority for Shibboleth (although
> I may need to take some time away from Shibboleth work to do a krb5 upload
> and some Policy and lintian work first).

Do you think I'd better look for a sponsor on debian-mentors?  If
somebody is willing to check a couple of things out that could help
moving forward faster and reduce your load at the same time.  As I
understand it, uploading this chain of dependent packages will take a
month at least (as each has to spend 10 days in the new queue).  Can
you estimate how much time we have before Lenny freezes?

As a side note, during the xmltooling initial upload a non packaging
related change got into the debian branch (the workaround for  That should
probably be moved into its own branch.  What naming scheme would you

Similarly, do you mind if I split off an etch branch from the debian
branch for backport work?  Would it also warrant another integration
branch besides master?

More information about the Pkg-shibboleth-devel mailing list