Shibboleth 2.0 SP packages look ready

[Ferenc Wagner]

Russ Allbery <rra at debian.org> writes:

> I've successfully tested against TestShib using Shibboleth 2.0, so it
> looks like the package stack is basically working.  I'm going to git push
> the final changes and do a final build and make sure I've taken care of
> the remaining lintian warnings and then upload for NEW processing.

Thank you very much for getting this far!  Honestly, I didn't hope you
could do the upload in the first turn.  Especially not ripe with man
pages and documentation!

Btw. git-buildpackage doesn't run lintian for me in pbuilder.  It's
installed, I can invoke it after pbuilder --login, but no automatic
joy...  What can be the problem?

Similarly, is there a way to get a prompt in the chroot if the build
fails?  Inserting those #include <memory> directives one-by-one wasn't
exactly fun when I had to restart compilation after each failure.
Sure, I worked around it by putting while ! $(MAKE); do /bin/bash;
done in debian/rules after some iterations, but that still doesn't
work well because bash exits like stdin was /dev/null or similar.

> I'll make the optimistic assumption that we'll figure out something for
> the OASIS schemas.
>
> This morning, I remembered the in-Debian precedent that I was trying to
> think of in the earlier discussion.  The OpenLDAP packages include schemas
> for LDAP that are extracted from IETF RFCs, which are covered under
> basically the same license as the OASIS protocol specifications.  We had
> to strip all the explanatory text out, but the actual schema definitions
> were considered an acceptable copyright risk to include in Debian under
> the DFSG.  The OASIS schemas seem like a very similar case to me.  (I make
> no statement here on the legal sufficiency or correctness of Debian's
> position here, just noting what Debian does in other cases.)

This sounds reasonable.  Our schema files haven't got much explanatory
text anyway.
-- 
Regards,
Feri.