Summary: | emerge -uD world thinks that x11-base/xfree is a dependency of wxGTK when it isn't. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Wolf <wolf_99> |
Component: | [OLD] Unspecified | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | greg_g |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 45610 |
Description
Wolf
2004-05-01 10:11:35 UTC
have you tried to recompile wxGTK against xorg-x11? Yes. I have wxGTK compiled uginst xorg-x11 (I compiled it after I compiled xorg-x11, and have compiled it sevral times). I whent us much us to unmerge aMule and wxGTK, I still get this messege: !!! all ebuilds that could satisfy "x11-base/xfree" have been masked. !!! possible candidates are: - x11-base/xfree-4.3.0-r5 (masked by: package.mask) - x11-base/xfree-4.3.99.902-r2 (masked by: package.mask, ~keyword) - x11-base/xfree-4.3.0-r6 (masked by: package.mask, ~keyword) !!! (dependency required by "dev-ml/lablgl-0.99-r1" [ebuild]) !!! Problem with ebuild net-p2p/mldonkey-2.5.18 !!! Possibly a DEPEND/*DEPEND problem. !!! Depgraph creation failed. Note: lablgl-0.99-r1.ebuild depends on virtual/x11 NOT on x11-base/xfree. :-/ I've got the same symptoms with other packages having dependancies changes. I noticed packages intalled on the system keep the dependances ans use flags at the time they where emerged. I switched from xfree to xorg-x11 too and I re-emerged many packages until having "emerge -bpuvD world" with no errors. Did you try "qpkg -I -q xfree" (should be empty)? I always build binary package. I rebuild every packages in /usr/portage/packages/All returned by command "grep xfree *.tbz2" (should be empty). Hope this helps. I've been having exactly the same problem. That is, when I try to emerge world, portage tries to install xfree rather than using xorg-x11, though the latter is in the virtuals file. I believe I have just discovered my problem: the only xorg-x11 ebuild has a keyword of ~x86, but my normal keyword is x86. I added a line to /etc/portage/package.keywords to specify that xorg-x11 should always use ~x86 and it seems to have solved the problem. If you're unable to resolve this by remerging specific packages that come up, please file a bug on each package. Also keep in mind comment #4, for those of you running stable systems. |