Summary: | gnome-base/eel-2.22.2 fails to compile against gnome-base/gnome-desktop-2.24.0 (gnome_bg_set_uri undefined) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | James Erickson <psykojime> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | brent.saner, dagger, death, denny.reeh, jeremyhu, johannis.gdev, psykojime, robert.bradbury, Sergiy.Borodych, vapier, wuddja, yoel |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 238650 |
Description
James Erickson
2008-10-20 02:09:57 UTC
Have the same problem on the same platform. Symbol gnome_bg_set_uri defined in the: /usr/lib/libgnome-desktop-2.so.2 -> libgnome-desktop-2.so.2.4.8 But libeel2 is linking with the /usr/lib64/libgnome-desktop-2.so and got unresolved symbol. CCing the portage crew, since this may only happen when the old libgnome-desktop is hanging around... *** Bug 242866 has been marked as a duplicate of this bug. *** Yoel, I've marked your bug as a duplicate, but it pointed out that you're getting gnome-desktop-2.24.0 and trying to compile 2.22 packages against it. This probably won't work, and hopefully the latest eel will come along soon and get it all going smoothly again. This isn't really a portage bug, so I've removed their CC again (sorry for the spam guys). Since you're running ~amd64, unfortunately you'll have to expect small breakages like this from time to time. Sorry about that. 5:( In the interim, you should probably downgrade and wait a couple of days for the new eel, or if you're really impatient, go get the gnome overlay to tide you over for the few days whilst they move everything into the main tree... eel from the gnome overlay is working great :)
>>> Installing gnome-base/eel-2.24.0
2.24 in overlay instead of 2.22 in the main tree.
yep, eel 2.22 doesn't want to work against gnome-desktop 2.24 Some other packages break too (which depends on eel) - like: nautilus, gnome-settings-daemon. piasekr@rob ~ $ ldd -r -v $(which nautilus) | grep eel libeel-2.so.2 => /usr/lib/libeel-2.so.2 (0x00007fe50d2ee000) undefined symbol: gnome_bg_changes_with_size (/usr/lib/libeel-2.so.2) undefined symbol: gnome_bg_set_placement (/usr/lib/libeel-2.so.2) undefined symbol: gnome_bg_set_uri (/usr/lib/libeel-2.so.2) undefined symbol: gnome_bg_set_pixmap_as_root (/usr/lib/libeel-2.so.2) undefined symbol: gnome_bg_is_dark (/usr/lib/libeel-2.so.2) undefined symbol: gnome_bg_set_color (/usr/lib/libeel-2.so.2) undefined symbol: gnome_bg_new (/usr/lib/libeel-2.so.2) undefined symbol: gnome_bg_create_pixmap (/usr/lib/libeel-2.so.2) undefined symbol: gnome_desktop_item_new_from_uri (/usr/bin/nautilus) undefined symbol: gnome_desktop_item_get_string (/usr/bin/nautilus) undefined symbol: gnome_desktop_item_get_entry_type (/usr/bin/nautilus) undefined symbol: gnome_desktop_item_get_localestring (/usr/bin/nautilus) undefined symbol: gnome_desktop_item_copy (/usr/bin/nautilus) undefined symbol: gnome_desktop_item_ref (/usr/bin/nautilus) undefined symbol: gnome_desktop_item_set_location (/usr/bin/nautilus) undefined symbol: gnome_desktop_item_new_from_string (/usr/bin/nautilus) undefined symbol: gnome_desktop_item_set_string (/usr/bin/nautilus) undefined symbol: gnome_desktop_item_unref (/usr/bin/nautilus) undefined symbol: gnome_desktop_item_set_localestring (/usr/bin/nautilus) undefined symbol: gnome_desktop_item_save (/usr/bin/nautilus) /usr/lib/libeel-2.so.2: Strange, i have no problems at all. $ ldd -r -v $(which nautilus) | grep eel libeel-2.so.2 => /usr/lib/libeel-2.so.2 (0x00007fd6838f9000) /usr/lib/libeel-2.so.2: $ epm -q nautilus nautilus-2.24.0 gnome-desktop-2.24 has been masked earlier today. Resyncing should take care of the problem, at least for now. Thanks *** Bug 243080 has been marked as a duplicate of this bug. *** *** Bug 243302 has been marked as a duplicate of this bug. *** *** Bug 244016 has been marked as a duplicate of this bug. *** *** Bug 245407 has been marked as a duplicate of this bug. *** *** Bug 245407 has been marked as a duplicate of this bug. *** proper version of eel is in the tree. 2.24 is in tree and now unmasked so when you upgrade you just have to use emerge @preserved-rebuild or revdep-rebuild. Yes, 2.24 is gradually leaking into the source tree as a complete package (see other bugs I have recently filed relating to the incomplete release problems). But *have* you updated the documentation so that people can research what is involved in @preserved-rebuild? Precisely where are the source files kept that generate this list of what is to be rebuilt and whether or not (or where) there is an archived list of such packages? Having spent several hours trying to track this down, I would suggest that proposing solutions which depend upon undocumented features is almost as bad as creating the features (without documenting them) in the first place. There was an OR in there. @preserved-rebuild OR revdep-rebuild. If you don't know the former, maybe it's a good idea to fall back to the latter? @preserved-rebuild is a special set in portage-2.2 that dynamically includes packages that need a rebuild to stop using a library version that is not owned by anything really anymore, but was preserved as a portage-2.2 feature to not break things too badly (remember expat for example), but yet complain loudly after most emerge operations that you need to do the rebuilds to get a clean working system. It is documented in portage-2.2 related documentation, which hasn't entered the handbooks yet, because remember -- you are using ~arch here. *** Bug 248125 has been marked as a duplicate of this bug. *** |