Shibboleth Developers

[Bernd Oberknapp <>]

On Thu, 22 Oct 2009, Scott Cantor wrote:

> Bernd Oberknapp wrote on 2009-10-22:
> > update succeeded. Adding obsoletes dependencies to the renamed packages
> > probably would allow an automatic update of log4shib and xmltooling, too.
> 
> All of them would conflict, right? Not just those two...

Surprisingly, no.

shibboleth, opensaml and xml-security-c are recognized as updates for
the existing RPM packages created from SRPMs. The only problem is that
libxmltooling and liblog4shib aren't recognized as updates for
xmltooling and log4shib. When updating from 2.2-3 these packages simply
are not installed. When updating from 2.1-1 yast complains that
xml-security-c requires a newer xmltooling version, and if I select to
uninstall xmltooling to resolve this conflict yast automatically pulls
in libxmltooling and the other new packages to resolve the dependencies.

Installing liblog4shib in parallel with log4shib also works fine, and
reoving log4shib doesn't break liblog4shib. Same for libxmltooling and
xmltooling and the other packages. If devel packages are installed I get
more warnings that newer versions are required but again when I select
to deinstall the old packages to resolve the conflicts the update works
fine.

Therefore my conclusion that if libxmltooling and liblog4shib would
be recognized as updates for xmltooling and log4shib an automatic update
of all packages would be possible.

The update from 2.2 and 2.1 also preserves an existing /etc/init.d/shibd
as /etc/init.d/shibd.rpmorig and a changed /etc/apache2/conf.d/shib.conf
as shib.conf.rpmsave

If this is different from Red Hat/CentOS, maybe there's some yast/zypper
magic involved?

Best regards,
Bernd

-- --------------------------------------------------------------------- --
Dipl.-Math. Bernd Oberknapp          Universitaetsbibliothek Freiburg
Tel: +49-761 / 203-3852              Rempartstrasse 10-16  | Postfach 1629
Fax: +49-761 / 203-3987              79098 Freiburg        | 79016 Freiburg