[Bug 343847] New: commoncpp2-1.5.7 breaks ABI compatibility
https://bugzilla.novell.com/show_bug.cgi?id=343847 Summary: commoncpp2-1.5.7 breaks ABI compatibility Product: openSUSE 10.3 Version: Final Platform: All OS/Version: All Status: NEW Severity: Blocker Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: reisenweber@web.de QAContact: qa@suse.de CC: mskibbe@novell.com Found By: Other starting a binary that's compiled against <= /usr/lib/libccgnu2-1.5.so.0.0.2 crashes with twinkle: symbol lookup error: twinkle: undefined symbol: _ZN3ost6Thread9isRunningEv Due to lazy binding this happens at arbitrary point in time. (use "LD_BIND_NOW=t twinkle" to get error at startup) This lib MUST be replaced by backward compatible version ASAP (=tomorrow)! Apps linked against the new broken version have to be updated too! see: http://www.nabble.com/Bug-402509:-crash-on-call-end-t2790937.htm http://tech.groups.yahoo.com/group/twinklephone/message/2013 jOERG -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=343847#c1
joerg reisenweber
3.1.1. ...``.so'', followed by a period and a version number that is incremented *whenever_the_interface_changes*. 3.5. ...Usually you can update libraries without concern; if there was an API change, the library creator is supposed to change the soname. That way, multiple libraries can be on a single system, and the right one is selected for each program. complete §3.6. Incompatible Libraries!!!
-- 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.
Hmmm, this is not a nice situation indeed. Politely spoken ;-) It is probably best if new Twinkle RPM's declare a dependency on the latest libraries. This way one is force to upgrade to the newest library and the problem is solved. Well, this would help to avoid "new" twinkle crashing ungracefully on a "pre-1.5.3" OS - but just this and nothing more. The main problem however is "old" apps inevitably crashing on all future "new" OS, as well as generally cling to LSB and avoiding a "new OS epoch" because "nothing will ever be the same again". To me the better way seems to link "new" twinkles against a "new version"
https://bugzilla.novell.com/show_bug.cgi?id=343847#c2
--- Comment #2 from joerg reisenweber
https://bugzilla.novell.com/show_bug.cgi?id=343847
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=343847#c3
Ralf Haferkamp
https://bugzilla.novell.com/show_bug.cgi?id=343847
Ralf Haferkamp
https://bugzilla.novell.com/show_bug.cgi?id=343847#c6
--- Comment #6 from joerg reisenweber
https://bugzilla.novell.com/show_bug.cgi?id=343847#c7
Ralf Haferkamp
participants (1)
-
bugzilla_noreply@novell.com