Summary: | Portage does not emerge gnome-vfs-1.0.5-r3 before emerging control-center-1.4.0.5-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | wolf at ivix dot org <wolf> |
Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED WORKSFORME | ||
Severity: | minor | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
wolf at ivix dot org
2003-11-01 14:27:17 UTC
from your output I see:
> /var/tmp/portage/gnome-vfs-1.0.5-r3/image//usr/lib/vfsConf.sh: No such
file or
directory .
but control center shouldnt be looking inside the portage image for that,
it should be looking in /usr/lib/. can you verify you do actually have gnome-vfs-1.0.5
installed ? (qpkg -I -v gnome-vfs) and also please the output of 'grep "config_file"
/usr/bin/gnome-vfs-config'. thanks.
I do have gnome-vfs-1.0.5 installed now, as well as control-center. The point of opening up this bug was to investigate why, when I didn't have gnome-vfs installed on my system and I tried to emerge control-center, that gnome-vfs was picked up as a dependency and emerged first. try remerging gnome-vfs-1.0* , the path inside its config script is probably b0rked. This sometimes happens, but is often not reproducable. i'm closing this : the deps seem to be ok and the problem seems to be a local path problem and are probably not reproducable. This just shouldn't happen ;) |