During compilation, the gconf-sanity-check-2 announces that gconf should already be installed, but an "emerge gnome" from an otherwise gnome-less system does not automatically build gconf before trying to build gnome-session (2.4.0)
that shouldnt happen, gnome-session depends on libgnomeui depends on gconf.
just happened to me too. i verified too: foser's right. the dependencies should make this impossible...
I'd seen this happen on two machines here before i reported it, and i'm trying to reproduce it on a freshly built machine (i'm 100 packages into the 138 that are being built here for an emerge gnome). I've seen other portage quirks of not properly evaluating dependencies and virtuals when its been given multiple packages to compile. Its entirely possible that when i saw it this last time i'd lumped together an "emerge gnome evolution mozilla cups" or something of that nature. I am sure though that i hadn't tried to bypass anything or give a --nodeps to the emerge, and gnome-session did give me the gconf-sanity-check-2 error.
Created attachment 18389 [details] emerge log OK, third machine in a row for me to give this error. I'm not imagining it. gconf appears to have been installed early on in the process, but somewhere between then and now, it broke. Using $(sysconfdir)/gconf/schemas/ as install directory for schema files checking for gconf-sanity-check-2... no configure: error: gconf-sanity-check-2 executable not found in your path - should be installed with GConf !!! ERROR: gnome-base/gnome-session-2.4.0 failed. !!! Function econf, Line 324, Exitcode 1 !!! econf failed Gentoo root # emerge -p gconf These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] gnome-base/gconf-2.4.0.1
and if you recompile it, it gets build i assume ?
yes. after that, i "emerge gconf" then "emerge gnome" and it finishes just fine. gconf itself seems to build the right files... is something else wiping out the sanity check file? looking at the build order, gconf-editor was built just 4 packages prior to the gnome-session that complained about it being missing.
*** Bug 30175 has been marked as a duplicate of this bug. ***
I've done today a fresh install, with an "emerge gnome" after the system emerge, and noticed the same bug. Looking at the timestamps in my portage log dir, I've seen that gconf is built before GTK2. But if you look at gconf auto{make|conf} files, you'll see that gconf-sanity-check is only built if GTK2 is installed... Hence, I think a dependency from gconf on gtk2 would solve this issue. I've also checked that it doesn't introduce anything circular in the deps, and it's okay.
dependency on gtk+-2 added
