117359 – Cannot resolve a virtual package name to an ebuild.

Bug 117359 - Cannot resolve a virtual package name to an ebuild.

Summary: Cannot resolve a virtual package name to an ebuild.

Status:	RESOLVED DUPLICATE of bug 114798

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-01-01 09:35 UTC by gilhad
Modified:	2006-01-01 09:36 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description gilhad 2006-01-01 09:35:55 UTC

I run emerge sync and was told:
>>> Updating Portage cache:   90%!!! Cannot resolve a virtual package name to an ebuild.
!!! This is a bug, please report it. (virtual/libstdc++-3.3)


(longer list is here:

Number of files: 132849
Number of files transferred: 60792
Total file size: 109272606 bytes
Total transferred file size: 71139312 bytes
Literal data: 71139312 bytes
Matched data: 0 bytes
File list size: 3102891
Total bytes written: 1216021
Total bytes read: 76979432

wrote 1216021 bytes  read 76979432 bytes  106316.05 bytes/sec
total size is 109272606  speedup is 1.40

>>> Updating Portage cache:   90%!!! Cannot resolve a virtual package name to an ebuild.
!!! This is a bug, please report it. (virtual/libstdc++-3.3)
)

Comment 1 Alec Warner (RETIRED) archtester

2006-01-01 09:36:37 UTC


*** This bug has been marked as a duplicate of 114798 ***