Plans for Shibboleth SP 2.1 debian packages
Russ Allbery
rra at debian.org
Thu May 7 18:00:51 UTC 2009
Ferenc Wagner <wferi at niif.hu> writes:
> Russ Allbery <rra at debian.org> writes:
>> Still on my list, but I've been swamped. Sorry. :/ They're
>> installable from testing right now, and with the new symbols handling
>> we're in much better shape for cherry-picking packages from testing
>> than we used to be, but I do still think that a regular backport
>> build would be useful just to guarantee that you don't pull in a
>> libstdc++ update or something later on.
> I thought that a proper pinning setup (which is necessary with
> backports all the same) wouldn't allow this.
I think that if the new version of Shibboleth from testing depends on a
new version of libstdc++, your pin of Shibboleth will pull it in.
> Anyway, making a Lenny backport means creating a new branch, inventing
> a new version number, rebuilding in a Lenny environment and uploading,
> right? It's pure administration, no techical work is needed, as far
> as I know. Which means I can't help with it.
Right.
> The Etch backport is also ready, we have been using it for a while.
> Tell me if I can be of any help.
Will do, but I think it mostly just requires me finding a couple of
hours and doing the builds.
--
Russ Allbery (rra at debian.org) <http://www.eyrie.org/~eagle/>
More information about the Pkg-shibboleth-devel
mailing list