checking for GNOME_MOUNT... configure: error: Package requirements (gnome-keyring-1 >= 0.4 libgnomeui-2.0 >= 2.1.5 dbus-glib-1 >= 0.31 hal-storage >= 0.5.7 gtk+-2.0 >= 2.8.0) were not met: No package 'libgnomeui-2.0' found
Clearly not missing, read the ebuild ;) Which version you have installed? Also attach the config.log and emerge --info.
the same happened to me when im trying to migrate to gcc-4.1.1-r1 from 3.3.6. in the midlle of emerging world this bug bubbles up. it seems there is something strange in calculating dependencies. below i attach output of the emerge world -pvt - gnome-mount is there on top-level(but i dont have it in world file) and no dependency to libgnomeui. however, when i made emerge -av1 gnome-mount, the dependency to lingnomeui is there and the whole merge proceed without problems.
Created attachment 104635 [details] world dependencies
Created attachment 104636 [details] emerge info
Same error here during a fresh Gentoo install. I did: - install stage3 - sync portage - install some system tools (vixie-cron, syslog-ng, ...) - emerge --update --deep world - emerge gnome During the "emerge gnome" the error occurred at the merge of gnome-mount-0.4-r5. I'll attach config.log and emerge --info.
Created attachment 105435 [details] Output of emerge --info
Created attachment 105436 [details] config.log of gnome-mount-0.4-r5
*** Bug 159106 has been marked as a duplicate of this bug. ***
You need to reopen the bug after providing the info; noone will ever notice again otherwise...
(In reply to comment #9) > You need to reopen the bug after providing the info; noone will ever notice > again otherwise... OK. OTOH I seem to remember that my only choice was to leave the bug status as is (right now the only option I have is to "Leave as NEW"). But I may have overlooked the possibility to reopen the bug after I added the info. BTW, a bug status of "RESOLVED" with resolution "NEEDINFO" seems a bit strange to me. Anyway: thanks for reopening this.
Do you have libgnomeui on your system? You don't have any overlays set in your emerge info... libgnomeui is the first dep in the ebuild for gnome-mount, so it *should* be being pulled in. Can you look at your gnome-mount ebuild and see if it has the dep?
(In reply to comment #11) > Do you have libgnomeui on your system? Yes, now I have. I merged it manually to make the error go away. > You don't have any overlays set in your > emerge info... libgnomeui is the first dep in the ebuild for gnome-mount, so > it *should* be being pulled in. As I said in Comment #5 this was a completely new Gentoo installation and the list of packages pulled by "emerge gnome" did pull gnome-mount before libgnomui. > Can you look at your gnome-mount ebuild and see if it has the dep? It has libgnomeui as runtime dependency (shouldn't libgnomeui also be a build dependency?): ---------- snip ---------- IUSE="debug" RDEPEND=">=gnome-base/libgnomeui-2.13 >=sys-apps/hal-0.5.7-r1 >=x11-libs/gtk+-2.8 gnome-base/gnome-keyring >=gnome-base/libglade-2 >=gnome-base/gconf-2 || ( >=dev-libs/dbus-glib-0.71 ( <sys-apps/dbus-0.90 >=sys-apps/dbus-0.60 ) )" DEPEND="${RDEPEND} dev-util/pkgconfig >=dev-util/intltool-0.29" DOCS="AUTHORS ChangeLog HACKING INSTALL NEWS README TODO" ---------- snap ----------
DEPEND="${RDEPEND} ^^^ all runtime dependencies are also build-time dependencies. Probably a circular dependency issue, about which there are other bugs open too
Just ran into this bug too, when emerging GDM on my Xfce-only system. Things were going just fine until gnome-mount started to be emerged. Got the same error: "No package 'libgnomeui-2.0' found" Can we get this fixed right away, especially if it's a circular dep as leio suggests? Thanks.
So, there is some kind of circular dep involved, because emerging libgnomeui does pull in gnome-mount (after libgnomeui, incidentally...) I'll look into this.
Okay, the circular dep is gnome-mount -> libgnomeui -> gnome-vfs -> gnome-mount. The deps are actually correct, since gnome-vfs has a PDEPEND on gnome-mount, so it's must actually be a portage bug.
OK. I've been seeing this exact same thing for some time now when doing pre-release builds. Is there anything that I can do to help, because as it stands right now, GNOME is broken for the release.
I thought the portage guys were already CC'd, but apparently not. Portage devs: How can we fix this? The depends appear to be correct. Is there something I'm missing? Or is this really a portage bug?
(In reply to comment #18) > Portage devs: How can we fix this? The depends appear to be correct. Is > there something I'm missing? Or is this really a portage bug? With versions of portage <2.1.2 there was never really any guarantee that a packages dependencies would actually be installed before the package itself. That issue is fixed in portage-2.1.2 (bug #147766) so that correct merge order is always guaranteed and circular dependencies will be reported if they exist.
Zac, can you write a little GWN article and/or forum post about this new behavior (what it does/why it's needed/how to avoid the problem) so people have a reference? People generally get confused if something used to work and breaks now with no explanation (e.g. http://forums.gentoo.org/viewtopic-t-539520.html)
Okay. With portage 2.1.2-r9 (current stable), this works fine. With portage 2.1.2_rc2-r1 (oldest version I have lying around on a machine), this fails. So, I'm going to mark this fixed. If people still have problems with portage 2.1.2-r9 or newer, please re-open.
