Description of problem: There is no /usr/lib/libudev.so.0. It is needed fo some third party software (for example Google Chrome browser). It should be a link to /usr/lib/libudev.so.1.1.5. ___________________________________ Version-Release number of selected component (if applicable): systemd-libs-194-1.fc18.i686 ___________________________________ How reproducible: Always ___________________________________ Steps to Reproduce: 1. Install Google Chrome browser from here: https://www.google.com/intl/en/chrome/browser/ 2. Try to launch it ___________________________________ Actual results: It needs /usr/lib/libudev.so.0, doesn't start. ___________________________________ Expected results: Google Chrome browser starts and works well. ___________________________________ Additional info: Work around: ln -s /usr/lib/libudev.so.1.1.5 libudev.so.0
There may be a case for adding the old library as a compat library - however, it changed from libudev.so.0 to libudev.so.1 for a reason - it changed ABI. Attempting to work around that via symlinking the library is a hack that only happens to work if you get lucky.
(In reply to comment #1) > There may be a case for adding the old library as a compat library - > however, it changed from libudev.so.0 to libudev.so.1 for a reason - it > changed ABI. Attempting to work around that via symlinking the library is a > hack that only happens to work if you get lucky. Then maybe it's a nice idea - to add the previous version of library into the package (or to create the separate package with an old one)?
It should be OK to simply install the f17 library package, right, Kay? Should we close the bug?
Regarding the code and file conflicts it should work, yes. Not sure about the implications with packaging, because people asked us to add: Obsoletes: libudev < 183 to the current systemd package.
Based on the above, what I should do now?
For the time being: ln -s libudev.so.1 /usr/lib64/libudev.so.0
Current google-chrome runs, they worked around it by shipping a symlink themselves. *** This bug has been marked as a duplicate of bug 883751 ***