On Tue, Nov 18, 2008 at 16:48, bart <[EMAIL PROTECTED]> wrote:
>
>> Hmmm - thats really weird.
>>
>> The liblrm.so.2 dependancy is an automatic one based the liblrm
>> shared
>> library that Pacemaker was built against.
>> Perhaps you were unlucky and mirrored the repo at a point when it was
>> rebuilding... refreshing your local mirror might help.
>>
>> As an advantage, you'll get the 1.0.1 update from earlier today :-)
>>
>
> Thanks! I just synced, and the problem appears to be still here:
>
> [EMAIL PROTECTED] scripts]# yum update
> Loading "fastestmirror" plugin
> Loading mirror speeds from cached hostfile
>  * CentOS-5.1-epel-x86_64: 192.168.0.4
>  * CentOS-5.1-extras-x86_64: 192.168.0.4
>  * CentOS-5-x86_64: 192.168.0.4
>  * CentOS-5-updates-x86_64: 192.168.0.4
>  * CentOS-5.1-extra-x86_64: 192.168.0.4
>  * CentOS-5-novell-x86_64: 192.168.0.4
>  * CentOS-5.1-testing-x86_64: 192.168.0.4
>  * CentOS-5.1-dagwieers-x86_64: 192.168.0.4
> Setting up Update Process
> Resolving Dependencies
> --> Running transaction check
> ---> Package pacemaker.x86_64 0:1.0.1-1.1 set to be updated
> ---> Package heartbeat.x86_64 0:2.99.2-4.1 set to be updated
> ---> Package heartbeat-common.i386 0:2.99.2-4.1 set to be updated
> --> Processing Dependency: liblrm.so.2 for package: heartbeat-common
> ---> Package libheartbeat2.x86_64 0:2.99.2-4.1 set to be updated
> ---> Package heartbeat-resources.i386 0:2.99.2-4.1 set to be updated
> ---> Package libxml2-python.x86_64 0:2.6.26-2.1.2.7 set to be updated
> ---> Package heartbeat.i386 0:2.99.2-4.1 set to be updated
> ---> Package pacemaker.i386 0:1.0.1-1.1 set to be updated
> --> Processing Dependency: liblrm.so.2 for package: pacemaker
> --> Finished Dependency Resolution
> --> Running transaction check
> ---> Package pacemaker.x86_64 0:1.0.1-1.1 set to be updated
> ---> Package heartbeat.x86_64 0:2.99.2-4.1 set to be updated
> ---> Package heartbeat-common.i386 0:2.99.2-4.1 set to be updated
> --> Processing Dependency: liblrm.so.2 for package: heartbeat-common
> ---> Package libheartbeat2.x86_64 0:2.99.2-4.1 set to be updated
> ---> Package heartbeat-resources.i386 0:2.99.2-4.1 set to be updated
> ---> Package libxml2-python.x86_64 0:2.6.26-2.1.2.7 set to be updated
> --> Processing Dependency: liblrm.so.2 for package: pacemaker
> ---> Package libxml2.x86_64 0:2.6.26-2.1.2.7 set to be updated
> --> Running transaction check
> ---> Package heartbeat-common.i386 0:2.99.2-4.1 set to be updated
> --> Processing Dependency: liblrm.so.2 for package: heartbeat-common
> ---> Package pacemaker.i386 0:1.0.1-1.1 set to be updated
> --> Processing Dependency: liblrm.so.2 for package: pacemaker
> --> Finished Dependency Resolution
> Error: Missing Dependency: liblrm.so.2 is needed by package heartbeat-common
> Error: Missing Dependency: liblrm.so.2 is needed by package pacemaker
>
> I do not see a package librm on the SuSe mirror, and it's doesn't appear to 
> be available anywhere else... Isn't that the problem??

No.  liblrm.* is be in libheartbeat2

[EMAIL PROTECTED] pacemaker $ wget
http://download.opensuse.org/repositories/server:/ha-clustering/CentOS_5/i386/libheartbeat2-2.99.2-4.1.i386.rpm
20:39:17 (13.59 MB/s) - `libheartbeat2-2.99.2-4.1.i386.rpm' saved
[193175/193175]

[EMAIL PROTECTED] pacemaker $ rpm -qlp libheartbeat2-2.99.2-4.1.i386.rpm
warning: libheartbeat2-2.99.2-4.1.i386.rpm: Header V3 DSA signature:
NOKEY, key ID 1d362aeb
/usr/lib/libapphb.so.2
/usr/lib/libapphb.so.2.0.0
/usr/lib/liblrm.so.2                   <------- here
/usr/lib/liblrm.so.2.0.0
/usr/lib/libpils.so.2
/usr/lib/libpils.so.2.0.0
/usr/lib/libplumb.so.2
/usr/lib/libplumb.so.2.0.0
/usr/lib/libplumbgpl.so.2
/usr/lib/libplumbgpl.so.2.0.0
/usr/lib/libstonith.so.1
/usr/lib/libstonith.so.1.0.0
[EMAIL PROTECTED] pacemaker $

[EMAIL PROTECTED] pacemaker $ rpm -q --provides -p
libheartbeat2-2.99.2-4.1.i386.rpm
warning: libheartbeat2-2.99.2-4.1.i386.rpm: Header V3 DSA signature:
NOKEY, key ID 1d362aeb
libapphb.so.2
liblrm.so.2       <---- here again
libpils.so.2
libplumb.so.2
libplumbgpl.so.2
libstonith.so.1
libheartbeat2 = 2.99.2-4.1

Comparing that to the x86_64 packages...

[EMAIL PROTECTED] pacemaker $ rpm -q -l -p libheartbeat2-2.99.2-4.1.x86_64.rpm
warning: libheartbeat2-2.99.2-4.1.x86_64.rpm: Header V3 DSA signature:
NOKEY, key ID 1d362aeb
/usr/lib64/libapphb.so.2
/usr/lib64/libapphb.so.2.0.0
/usr/lib64/liblrm.so.2
/usr/lib64/liblrm.so.2.0.0
/usr/lib64/libpils.so.2       <--- as expected
/usr/lib64/libpils.so.2.0.0
/usr/lib64/libplumb.so.2
/usr/lib64/libplumb.so.2.0.0
/usr/lib64/libplumbgpl.so.2
/usr/lib64/libplumbgpl.so.2.0.0
/usr/lib64/libstonith.so.1
/usr/lib64/libstonith.so.1.0.0
[EMAIL PROTECTED] pacemaker $

[EMAIL PROTECTED] pacemaker $ rpm -q --provides -p
libheartbeat2-2.99.2-4.1.x86_64.rpm
warning: libheartbeat2-2.99.2-4.1.x86_64.rpm: Header V3 DSA signature:
NOKEY, key ID 1d362aeb
libapphb.so.2()(64bit)
liblrm.so.2()(64bit)       <--- could these extra brackets be the issue?
libpils.so.2()(64bit)
libplumb.so.2()(64bit)
libplumbgpl.so.2()(64bit)
libstonith.so.1()(64bit)
libheartbeat2 = 2.99.2-4.1
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to