Summary: | x11-libs/libX11-1.3.2 apparently missing dependenies on x11-libs/libXext and missing dependency on x11-libs/libXxf86vm | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cyp <cyp561> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Cyp
2010-01-13 15:29:59 UTC
x11-libs/libXxf86vm builds with "emerge --nodeps", (had libX11-1.2.2 installed). Hope that wasn't a bad idea... Probably you need to unmerge ghostscript for the moment, but that output suggests somebody just got burned by depclean ? (In reply to comment #2) > Probably you need to unmerge ghostscript for the moment, > but that output suggests somebody just got burned by depclean ? Some things were uninstalled due to being blockers, when trying to upgrade mesa (which meant having to upgrade xorg, too). I guess x11-libs/libXxf86vm-1.0.2 was one of them. No depclean involved. I reemerged x11-libs/libXxf86vm, in case anything broke in it when installing it with --nodeps. libX11 depends on ghostscript to compile the manual, and ghostscript's gs is linked against X apparently, so no, libX11 should not depend on a library that ghostscript can't find. Did you run revdep-rebuild yet? (In reply to comment #4) > libX11 depends on ghostscript to compile the manual, and ghostscript's gs is > linked against X apparently, so no, libX11 should not depend on a library that > ghostscript can't find. Did you run revdep-rebuild yet? I hadn't run revdep-rebuild. I just ran it, it found some things, but nothing in any way related (just libquicktime, things like that). "Forcing" it to build x11-libs/libXxf86vm first seems to have fixed the problem for me, and I didn't rebuild ghostscript. I guess the problem was some bad combination of blockers and dependencies (and probably the "doc" use flag), maybe I just upgraded at the wrong time. I don't remember now, whether it automatically uninstalled the blocked packages, or if I did it manually. OK, so the problem went away of its own accord. :) |