Shibboleth2 packaging

[Ferenc Wagner]

Russ Allbery <rra at stanford.edu> writes:

> For those who had started on Shibboleth 2.0 packaging, please send to the
> new pkg-shibboleth-devel lists links to download the *.dsc files for the
> current packages, and I can import those into Git and create new Git
> repositories for them so that we can start getting them ready for upload.

Hi Russ,

I was surprised you asked for the dsc files, but here they are:

Format: 1.0
Source: xmltooling
Version: 1.0-1
Binary: libxmltooling1-doc, xmltooling-schemas, libxmltooling1-dev, libxmltooling1
Maintainer: Debian Shib Team <pkg-shibboleth-devel at lists.alioth.debian.org>
Architecture: any
Standards-Version: 3.7.2
Build-Depends: debhelper (>= 5), autotools-dev, libxerces27-dev | libxerces28-dev, liblog4cpp5-dev, libxml-security-c-dev (>= 1.4), libcurl3-openssl-dev
Uploaders: Russ Allbery <rra at debian.org>
Files: 
 4e7c21608f0fbdcfd966263f0c350d99 549767 xmltooling_1.0.orig.tar.gz
 0566c04308eadfae167401f6f656a883 11119 xmltooling_1.0-1.diff.gz

Format: 1.0
Source: opensaml2
Version: 2.0-1
Binary: libsaml2-doc, opensaml2-schemas, libsaml2-dev, libsaml2
Maintainer: Debian Shib Team <pkg-shibboleth-devel at lists.alioth.debian.org>
Architecture: any
Standards-Version: 3.7.2
Build-Depends: debhelper (>= 5), autotools-dev, liblog4cpp5-dev, libxerces27-dev | libxerces28-dev, libxml-security-c-dev (>= 1.4), libxmltooling1-dev
Uploaders: Russ Allbery <rra at debian.org>
Files: 
 85968f3c72cb789b11c9d01209e4d46b 705058 opensaml2_2.0.orig.tar.gz
 2cbfe7f9d78ed68731de8394505037f7 11415 opensaml2_2.0-1.diff.gz

Format: 1.0
Source: shibboleth-sp
Version: 2.0-1
Binary: libapache2-mod-shib2, libshib2-dev, libshib2-doc
Maintainer: Ferenc Wagner <wferi at niif.hu>
Architecture: any
Standards-Version: 3.7.2
Build-Depends: debhelper (>= 5), autotools-dev, libxerces27-dev | libxerces28-dev, libsaml2-dev, libssl-dev, zlib1g-dev, liblog4cpp5-dev, apache2-threaded-dev, libxml-security-c-dev (>= 1.4)
Files: 
 0ac0dcb0ef367ef08bcbbb2c1e3330c4 728046 shibboleth-sp_2.0.orig.tar.gz
 0e4de74a4432893ab6012cec5e3ab6ed 21871 shibboleth-sp_2.0-1.diff.gz

They are based on the Internet2 sources appropriately renamed.  The
SP package is yet to be split up, its maintainer changed etc...

I'm about to upload the full package files somewhere, but some
questions arose:

 1. Should we use shibboleth-sp2 as the source package name?

 2. Should we package opensaml2-schemas or simply provide a newer
    version of your opensaml-schemas?

 2a. If the first, should that contain /usr/share/xml/opensaml2/* or
     stay with the current name and conflict with opensaml-schemas?
     This rules out the optional priority.

 3. Similar questions concerning the opensaml source package name.  If
    both versions are to be present in Debian they probably can't
    share the name of the source package.

 4. How will we manage the backports/sid and the 1/2 duality under
    Git?  Will shibboleth-sp have two branches for version 1 and 2 and
    four Debian branches for packaging each under Etch and Sid?
    Or will you create two repositories for the two major versions,
    and only two Debian branches under each (for Etch and Sid)?

 5. Should we submit ITP's for the above packages and refer to those
    numbers in the first changelog entry?

 6. Should we separate out the xmltooling-lite library into its own
    package?

 7. What's the preferred way to correctly determine the various
    (build) dependencies?

Sorry to overwhelm you with this bunch of (not too well organised)
questions, but the 9-hour time zone difference narrows the
communication opportunities so much...  If you could quicly answer at
least some of these questions (before I leave to bed) that would be a
big bonus: 2 exchanges instead of 1 per day! :)  Once we get up to
speed it won't be such an important issue.
-- 
Regards,
Feri.