#83 Cannot resolve a virtual package name to a ebuild

closed
nobody
None
5
2007-03-09
2006-01-05
Anonymous
No

When "emerge sync" is updating Portage cache I get the
error Cannot resolve a vertual package name to an
ebuild. Followed by the following message:
!!! This is a bug, please report it.
(virtual/libstdc++-3.3)
I installing it in coLinux following their instructions
on the wiki and may have messed up somewhere. This is
also the first time I ever tried coLinux on top of
windows and therefore couldn't setup the swap drive
following there instructions as well. So I was running
it without a swap drive with only 128MB of memory
allocated to it. There is nothing else I can say since
I don't know much about Gentoo or CoLinux yet. I have
attached a screen shot of the window for reference.

sybertek88.nospam<AT>hotmail.com

Discussion

  • Screen capture of window

     
  • Danny Staple
    Danny Staple
    2006-01-06

    Logged In: YES
    user_id=748225

    Have you tried checking the gentoo forums at
    http://forums.gentoo.org?

    If this has been seen before, it is likely that it would
    have been posted there.

    Danny

     
  • René Berber
    René Berber
    2006-01-06

    Logged In: YES
    user_id=722526

    I ran into this problem too, and solved it after running
    into more problems that said, in short, that
    /etc/make.profile didn't point to the right place.

    I don't know if the Gentoo/kernel 2.6 image is faulty or the
    "emerge --sync" did broke that link, but I saw it was a
    symbolic link pointing to
    /usr/portage/profiles/default-linux/x86/2004.3/ which is a
    directory that doesn't exist.

    So remove and relink:

    # rm /etc/make.profile
    # ln -s /usr/portage/profiles/default-linux/x86/2005.1
    /etc/make.profile

    And try emerge again.

     
  • Danny Staple
    Danny Staple
    2006-01-09

    Logged In: YES
    user_id=748225

    Right - I know exactly what this is - having seen it before.
    There have been a few major changes to the portage tree, and
    that was one of them. Emerge sync without the changes will
    cause trouble.

    What it means is the image is out of date, and that it needs
    to be updated properly. Regular Gentoo users should read GWN
    to keep ahead of these, and the image may need updating in
    response to GWN announcements. The image is not faulty, just
    dated.

    Danny

     
  • Henry N.
    Henry N.
    2007-03-09

    • status: open --> closed
     
  • Henry N.
    Henry N.
    2007-03-09

    Logged In: YES
    user_id=579204
    Originator: NO

    should outdated with the new gentoo image Gentoo-colinux-i686-2007-03-03.7z on SF