Need help in shiibboleth upgrade from 2.3.1 to 2.4.3 on RH linux

[Shaik, Abdul (NBCUniversal)]

Thanks Scott for the clarification. 

Is there a documentation on how to remove the packages installed by
using
SRPMs(log4shib+opensaml+xerces+xmltooling etc).

I removed all the packages installed by RPM. I just want to make sure
that there
is nothing remained from the installation of SRPMs.

We initially installed shibboleth and other supporting packages on this
box
using SRPMs.

Appreciate your help on this.

--Kalam

-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net]
On Behalf Of Cantor, Scott
Sent: Monday, December 19, 2011 6:16 PM
To: users at shibboleth.net
Subject: Re: Need help in shiibboleth upgrade from 2.3.1 to 2.4.3 on RH
linux

On 12/19/11 5:39 PM, "Shaik, Abdul (NBCUniversal)"
<Abdul.Shaik at nbcuni.com> wrote:

>Hi All,
> 
>We are trying to upgrade
>shibboleth from 2.3.1 to 2.4.3 using rpm source.

You're mixing versions of packages during the build.

>The problem is when
>installing the packages libsaml7-2.4.3-3.1.i386.rpm and
>opensaml-bin-2.4.3-3.1.i386.rpm, it still requires old library from the
>previous installation:   error: Failed dependencies:

The only libraries it requires are the ones you build it against.

>libxml-security-c.so.15 is needed by libsaml7-2.4.3-3.1.i386 and it
>should look
>for new library libxml-security-c.so.16.

If it requires .so.15, then that's because the package(s) you had in
place
during the SRPM rebuild were from that version. Certainly the devel
package was.

> And we have both new and old library
>file: libxml-security-c.so.15 and libxml-security-c.so.16 needed to
>support the
>package

That doesn't matter. If the build is linked to one version, that's the
version that will be embedded in the RPM that results.

If you want to use xml-security-1.6.1 and build on a box that has a
running version of older software, you have to take care to remove at
minimum all the old -devel packages and install the new lib and -devel
packages along side the old lib packages rather than doing upgrades.
Then
the new builds on top will use the latest version found.

I would question why you're doing any of this. As long as RH4 remains
supported, which ends with the next release, but for now anyway, there's
no reason you should be building this from source. The shibboleth
package
alone might require a rebuild if your Apache isn't standard, but that
doesn't require rebuilding the rest.

You also shouldn't be trying to build a new set of packages on a machine
running an older version. You can, but you're not being successful, so
you
should consider using a clean box to build the packages and then
transfer
them.

-- Scott

--
To unsubscribe from this list send an email to
users-unsubscribe at shibboleth.net