thanks, 2.1, backports

[Peter Schober]

folks,

Just wanted to say thanks for your work. I just built an 2.0 SP on
Etch, with basically no changes. I also built an 2.1 SP on Etch, by
simply reusing the debian/ directory and upping the relevant version
numbers on those 3 packages via `dch --increment`.
(I didn't version the dependencies or build-dependencies, though.)
Seems to work just fine.

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?

I have a few questions though:

* Any chance 2.1 will make it into Lenny?
* If not, will you provide 2.1 backports for Lenny?
* Will you provide 2.x backports for Etch?

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
* xerces-c2 source package from Lenny (included in my backport)

The rest (xml-security-c, xmltooling, opensaml2 and shibboleth-sp2)
came from the git repos.

For my "brute-force" backporting I only changed:
* xml-security-c: --without-xalan
  because libxalan110-dev pulls in xerces27* with conflicts with my
  newly built libxerces-c2-dev

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

I also rebuilt shibboleth-sp2 with --disable-odbc but that's only a
personal preference (to keep dependencies smaller which means less
work for me).

best regards & thanks for your work so far,
-peter

-- 
peter.schober at univie.ac.at - vienna university computer center
Universitaetsstrasse 7, A-1010 Wien, Austria/Europe
Tel. +43-1-4277-14155, Fax. +43-1-4277-9140