On Thu, Nov 20, 2008 at 11:07, Andrew Beekhof <[EMAIL PROTECTED]> wrote: > On Thu, Nov 20, 2008 at 09:02, bart <[EMAIL PROTECTED]> wrote: >> >>> >>> Did you try installing with rpm instead of YUM? >>> _______________________________________________ >> >> Just did, but no luck. See output at the bottom of this post. >> >> I looked a little further on the current packages installed. I noticed >> /usr/lib/liblrm.so.0 is in libheartbeat2 > > ohhhhh > ok, then this _is_ the same as Alex's situation and was caused by me > not noticing that the liblrm.so version changed from .0 to .2 > > you can try his method for upgrading and see if that helps. > > > I can promise this wont happen again because the libheartbeat{X} > package will now only includes shared libraries ending with *.so.{X} > So the build will fail if the libraries change (and I dont update the > spec file) - which is something I'll definitely notice > >> I don't know the contents of de spec-file of >> libheartbeat2-2.99.2-3.1.x86_64.rpm, but wouldn't a "provides" statement for >> liblrm solve this issue? > > not really, because libheartbeat2 already contains this. > > [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 > libpils.so.2 > libplumb.so.2 > libplumbgpl.so.2 > libstonith.so.1 > libheartbeat2 = 2.99.2-4.1 > > although maybe a provides liblrm.so.0 would help
I've added this to the 2.99.2-6.1 version of the heartbeat packages (which are building at the moment) Can you give it a try and see if it resolves the issue? _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems