https://bugzilla.novell.com/show_bug.cgi?id=804202
https://bugzilla.novell.com/show_bug.cgi?id=804202#c10
Tim Serong changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tserong@suse.com
--- Comment #10 from Tim Serong 2013-09-27 12:43:59 UTC ---
I've got kind of a similar problem with Fedora 19. I'm building hawk in
network:ha-clustering:Stable, which has a binary which links against libcib,
which is provided by pacemaker-libs in Fedora. In Fedora 19 GA, it's
libcib.so.2, so my build wants that. On my Fedora 19 test VM, pacemaker-libs
from Fedora updates has libcib.so.3, so I can't actually install hawk, as it's
built against libcib.so.2. Leaving aside the fact that it seems to run OK if I
symlink libcib.so.2 to libcib.so.3 (yuck), this has got me thinking... If we
had a Fedora:$VER:Update project on OBS, that would continually need to be
refreshed, right? Any any packages dependent on it in OBS would continually
rebuild...?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.