I am attempting to update to the current stable portage release on a system that was built in May 2005. Portage installs fine, but upon resyncing, portage craps out with the following error: <snip> deleting app-accessibility/brltty/brltty-3.6.1.ebuild deleting app-accessibility/brltty/brltty-3.4.1.ebuild deleting app-accessibility/at-poke/files/digest-at-poke-0.2.1 deleting app-accessibility/at-poke/at-poke-0.2.1.ebuild deleting .keep Number of files: 132924 Number of files transferred: 71308 Total file size: 108925992 bytes Total transferred file size: 79250874 bytes Literal data: 79250874 bytes Matched data: 0 bytes File list size: 3148256 Total bytes written: 1426341 Total bytes read: 41726221 wrote 1426341 bytes read 41726221 bytes 66851.37 bytes/sec total size is 108925992 speedup is 2.52 >>> Updating Portage cache: 90%!!! Cannot resolve a virtual package name to an ebuild. !!! This is a bug, please report it. (virtual/libstdc++-3.3) </snip> it looks like the entry for libstdc++-v3 in the portage tree is incorrect.
*** This bug has been marked as a duplicate of 114798 ***
Er sorry, you said 2.0.53...got a little jumpy ;)
*** This bug has been marked as a duplicate of 116253 ***
(In reply to comment #3) > *** This bug has been marked as a duplicate of 116253 *** This has nothing in common with the above bug.
(In reply to comment #0) > >>> Updating Portage cache: 90%!!! Cannot resolve a virtual package name to an ebuild. > !!! This is a bug, please report it. (virtual/libstdc++-3.3) Well, portage-2.0.53 does not have the above error message in it's source code. Try `emerge -u portage && emerge --metadata` and that should fix it. If you continue to have problems, please post the output of `emerge --info`. *** This bug has been marked as a duplicate of 114798 ***
