Summary: | db-4.1.25 & pam-0.77 --deep dependancy issue. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Peter Beekman <pbeekm> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | deviantgeek |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Beekman
2003-12-19 18:02:48 UTC
Can't duplicate this. Masking problems are more than likely profile related. I can duplicate it ;-) It's happening here. Is there any info I can provide you with? My /etc/make.profile link was pointing to an older portage tree. I have "moved" my tree to /root/portage, and making the link point to the new /root/portage/profiles/default-x86-1.4/ fixed my problem. My old tree is still at /usr/portage, it is just not updated by emerge sync's. There is no such problem here, I'm not sure why the bug is marked 'resolved'. If the answer was in the previous comment, it escaped me. I have 2 systems that fail to work. How do you fix this? Please ignore the previous (as I'm assuming you have). It made no sense. I resolved this issue by removing berkdb from my USE flags. |