119922 – emerge --sync fails, "Cannot resolve a virtual package name to an ebuild."

Bug 119922 - emerge --sync fails, "Cannot resolve a virtual package name to an ebuild."

Summary: emerge --sync fails, "Cannot resolve a virtual package name to an ebuild."

Status:	RESOLVED DUPLICATE of bug 114798

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	x86 Linux

Importance:	High major (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-01-22 07:14 UTC by Chris Macrander
Modified:	2006-01-22 07:16 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 Chris Macrander 2006-01-22 07:14:25 UTC

When running emerge --sync on an x86 system that I hadn't sync-ed in a long time, this happened:
Updating Portage Cache:  90%!!!Cannot resolve a virtual package name to an ebuild.
!!!This is a bug, please report it. (virtual/libintl-0)

I tried to emerge the new version of portage and I got an error suggesting my portage tree was not complete.

I tried to emerge --sync again the next day and got them same error but this time the portage cache stopped at 88%

Before this happened the system was completely updated, i.e. several months ago I ran emerge --sync and emerge -u world

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2006-01-22 07:16:11 UTC

...

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