Summary: | Cannot resolve a virtual package name to an ebuild | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Freyr Gunnar Ólafsson <gnarlin> |
Component: | Unclassified | Assignee: | Lars Weiler (RETIRED) <pylon> |
Status: | VERIFIED NEEDINFO | ||
Severity: | major | CC: | 043936y, is, radek, vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Freyr Gunnar Ólafsson
2003-12-04 03:51:43 UTC
I can reproduce it on my stable x86-box with the (testing) cdrtools-2.01_alpha20 installed, when I run ACCEPT_KEYWORDS="~x86" emerge -DUp cdrdao (it's a dependency). I saw, that virtual/cdrtools is not listed in the profiles. But adding it locally didn't changed anything. Sorry, I don't know further. So I call vapier that he may help ;-) *** Bug 35302 has been marked as a duplicate of this bug. *** *** Bug 35856 has been marked as a duplicate of this bug. *** Does not seem to be valid any more after I added a newer version of cdrtools to portage. Maybe it could also have been a bug in portage. AFAIR there were some issues with virtual packages. May you test it? sorry man, i was totally unable to reproduce this :/ No problem. Let's wait a day or two what others in the Cc say. My problem was a missing entry in the virtuals file. Virtuals now it's ok, so I cannot reproduce this neither mine (35856) bug. Thanks for testing. I close this bug. |