Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 355651

Summary: gnome 3 libraries final release library name change upon final release breaks applications
Product: Gentoo Linux Reporter: Delan Azabani <delan>
Component: Current packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED INVALID    
Severity: normal CC: Marc-Antoine
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Delan Azabani 2011-02-20 07:08:28 UTC
Using the gnome overlay, today I did an emerge update, which pulled in the final releases of gtk and gdk (version 3, as opposed to 2.99). Oddly, the gtk library has moved from

/usr/lib64/libgtk-3.0.so.0.0.0
/usr/lib64/libgtk-3.0.so.0
/usr/lib64/libgtk-3.0.so

to

/usr/lib64/libgtk-3.so.0.0.0
/usr/lib64/libgtk-3.so.0
/usr/lib64/libgtk-3.so

which drops the '.0' after '3'. Similarly, gdk has moved from

/usr/lib64/libgdk-3.0.so.0.0.0
/usr/lib64/libgdk-3.0.so.0
/usr/lib64/libgdk-3.0.so

to

/usr/lib64/libgdk-3.so.0.0.0
/usr/lib64/libgdk-3.so.0
/usr/lib64/libgdk-3.so

This breaks programs such as =gnome-terminal-2.33.5, who try and load libgtk-3.0.so.0 and libgdk-3.0.so.0. I have worked around that by symlinking the old names to the new names. These are not the only two files that seem to be changed. Libraries like libgailutil-3.0.so[.0[.0.0]] have also dropped the first '.0', which, in that example, breaks nautilus.

Reproducible: Always

Steps to Reproduce:
1. update to the newest final gtk, gdk, and other gnome 3 libriaries
2. observe library name changes and nautilus, gnome-terminal etc. breaking

Actual Results:  
Name change breaks applications.

Expected Results:  
Either the applications should be updated to reflect the library name changes, or the libraries should not have been renamed.
Comment 1 Marc-Antoine Perennou 2011-02-20 08:37:40 UTC
Don't symlink, it's not a correct workaround. It's a known and wanted behaviour. Like each time this occurs, the right solution is obviously to run revdep-rebuild
Comment 2 Delan Azabani 2011-02-20 09:56:57 UTC
I didn't know this. Thanks for that.