John P. Burkett wrote: > Doing revdep-rebuild on an amd64 machine, I received a response > the included the following lines: > * All prepared. Starting rebuild > emerge --oneshot app-text/xpdf:0 > gnome-base/gnome-panel:0 > kde-base/kdegraphics:3.5 > mail-client/-MERGING-evolution:2.0 > media-plugins/gst-plugins-faad:0.8 > media-plugins/xmms-alsa:0 > media-plugins/xmms-vorbis:0 > media-video/totem:0 > .......... > Calculating dependencies... done! > emerge: there are no ebuilds to satisfy > "mail-client/-MERGING-evolution:2.0". > > After doing emerge -C evolution, I redid revdep-rebuild but got the same > response. After doing emerge evolution, I again redid revdep-rebuild, > with the same results. > > Suggestions for how to successfully run revdep-rebuild would be most > welcome. I'm willing to sacrifice evolution if that would help. > > Hmm, somehow portage got the idea there is a package named mail-client/-MERGING-evolution, which is false. If you are lucky: emerge -avC mail-client/-MERGING-evolution
Although that could fail, as package names aren't supposed to start with -, so who knows what portage does with it. Next shot, clear out anything you don't need (make sure to check the output, although these days this command is safe unless you have done something strange). emerge -av --depclean Final shot is to play around in /var/db/pkg. This is where portage keeps track of what is installed, and how, so messing around here is inherently unsafe. I have my suspicions as to the correct thing to do here, but I won't post it since I'm not terribly sure. Someone with more expertise could help here, but I suspect either method 1 or 2 will work. Nick
