Bug 39320

Summary:	Masked packages providing virtual packages cause emerge to fail
Product:	Portage Development	Reporter:	Danin Woldroffe <danin>
Component:	Core - Dependencies	Assignee:	Portage team <dev-portage>
Status:	RESOLVED DUPLICATE
Severity:	major
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Danin Woldroffe 2004-01-25 01:30:59 UTC

Specific reproduction, for me:
(With a x11-base/xfree already installed)
ACCEPT_KEYWORDS="~x86" emerge x11-base/xdirectfb
optional: emerge rsync
emerge world -up
 - Dep check fails - virtuals/x11
nano /var/cache/edb/virtuals
 - Locate this line:
   virtual/x11 x11-base/xdirectfb x11-base/xfree
 - Change it to read the following: (NOT delete x11-base/xdirectfb!)
   virtual/x11 x11-base/xfree x11-base/xdirectfb
emerge world -up
 - Works now.

To fix this, I assume the virtuals dep check system is failing to proceed checking virtuals after running into a masked package?

Reproducible: Always
Steps to Reproduce:
emerge x11-base/xfree
(emerge other programs?)
emerge x11-base/xdirectfb
(emerge rsync?)
emerge world -up
Actual Results:  
Virtuals/x11 dependancy check failed

Expected Results:  
World upgrade pretend listing...

...you know, I can work circles around alot of my friends..I spend hours in the
#gentoo channel helping people...but I really have no idea how to paste info
from the terminal here. How pathetic is that? lol...sorry. But I have tried this
on three computers now,

Comment 1 Nicholas Jones (RETIRED) gentoo-dev

2004-01-25 01:36:11 UTC

/etc/portage/package.keywords

nakano: another condition to check for?


As for getting info from the terminal...

emerge whatever &> file.log
Or... Do it in an [axE]term... Highlight with left click,
middle click (or both if you don't have a middle) over target
window... and you've just pasted.

Comment 2 SpanKY gentoo-dev

2004-01-25 01:38:15 UTC


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

Comment 3 Masatomo Nakano (RETIRED) gentoo-dev

2004-01-25 01:44:26 UTC

I think it was fix in portage-2.0.50_pre20
Can you try it?