thanks, 2.1, backports

[Russ Allbery]

Thank you very much for the feedback!

Peter Schober <peter.schober at univie.ac.at> writes:

> The only thing I noticed is that /var/log/shibboleth is being used but
> not created by any of the packages. Should I file a bug for this?

Yes, please.  We need logrotate rules for it as well.

> I have a few questions though:
>
> * Any chance 2.1 will make it into Lenny?

I'm afraid not.  Most of the compilation fixes in 2.1 are already in the
Debian package, I think, but any other improvements were too late to make
it into lenny.  New upstream versions are no longer allowed into the
release.

> * If not, will you provide 2.1 backports for Lenny?

Yes.

> * Will you provide 2.x backports for Etch?

That was the plan; I personally don't have a lot of time to work on that
at the moment, though.

> Jfyi, since I'm backporting this for a vendor in our federation (who's
> stuck on Etch and I want them to use SAML2/Shib2 now) here are my
> notes on my home-grown backporting efforts:
> ( See also https://aai-wiki.univie.ac.at/DebianEtch )
>
> For dependencies not available in Etch I used the following packages:
> * log4cpp from Etch backports, to at least get log4cpp up to 1.0

Yup, that's required.

> * xerces-c2 source package from Lenny (included in my backport)

I *think* that the Xerces-C from etch-backports would be fine.

> * xmltooling: s/libcurl3-openssl-dev/libcurl4-openssl-dev/
>   so I could reuse Etch's libcurl (instead of backporting libcurl
>   itself as well).

Yup, this should be safe.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>