So I tested the following on bionic, xenial and trusty (amd64):
a) piuparts install-purge and install-upgrade-purge tests
b) In the corresponding Docker container:
1. Install the whole Shibboleth SPv2 from the distribution's repositories
apt install libapache2-mod-shib2 libxmltooling-dev
2. Test shibd's configuration with
cd /etc/shibboleth; shib-keygen; shibd -t
3. service shibd start, then check that there are no errors in /var/log/shibboleth/shibd.log
4. Download the new xmltooling packages and install them (apt-get install ./*.deb)
5. service shibd restart, then check that there are no errors in /var/log/shibboleth/shibd.log
=> For me, the fixed xmltooling packages for bionic, xenial and trusty are OK :)
So I tested the following on bionic, xenial and trusty (amd64): upgrade- purge tests mod-shib2 libxmltooling-dev shibboleth/ shibd.log shibboleth/ shibd.log
a) piuparts install-purge and install-
b) In the corresponding Docker container:
1. Install the whole Shibboleth SPv2 from the distribution's repositories
apt install libapache2-
2. Test shibd's configuration with
cd /etc/shibboleth; shib-keygen; shibd -t
3. service shibd start, then check that there are no errors in /var/log/
4. Download the new xmltooling packages and install them (apt-get install ./*.deb)
5. service shibd restart, then check that there are no errors in /var/log/
=> For me, the fixed xmltooling packages for bionic, xenial and trusty are OK :)