I was emerging evolution and portage was emerging libgnome. I came back to my box to find the process stalled for several hours while it was installing schemas after compiling the package. I control-c'd out of the install and re-ran emerge evolution. Portage ignored the fact that libgnome hadn't been successfully installed and skipped on to the next ebuild in the dep list. It appears that portage updates its db of installed packages before the package is actually finished installing. emerge -s libgnome shows: * gnome-base/libgnome Latest version available: 2.2.2 Latest version installed: 2.2.2 Size of downloaded files: 883 kB Homepage: http://www.gnome.org/ Description: Essential Gnome Libraries I control-c'd out of the final post compile install task completion. I did a qpkg -l libgnome | wc and it has 380 items listed as being installed or touched by the install. I re-emerged it a second time without interrupting it, and it has 473 items being installed or touched. It isn't fully installed, it's actually missing a major part of the contents of the package.
Forgot portage rev: 2.0.48-r5
w/out more information (like an log of the original emerge) this bug really cant be tracked ... who is to say that the ebuild isnt at fault ?
If you need more info, please let me know specifically what you want, and I'll recreate it, since I've been able to recreate it numerous times.
This is a bug in portage. I recommend not control-C'ingout... as that is fairly hazardous to system-health in general. Half-installed glibc or gcc == pain.
This has been fixed with lockfiles. It's getting better in cvs.
