Summary: | media-video/nvidia-settings-1.0.20051122-r3 missing dependencies due to virtual/x11-7.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | P Nienaber <gentoobugs> |
Component: | New packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | aynjell, dominik, fredrik, jakub, jieryn, mellermeller, rusxakep, user00265 |
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
P Nienaber
2006-02-16 11:51:30 UTC
No, it isn't missing any dependencies, you are providing virtual/x11 or redefining the virtual in /etc/portage/profile/virtuals or doing another invalid stuff. <snip> DEPEND="virtual/libc >=x11-libs/gtk+-2 || ( ( x11-base/xorg-server x11-libs/libXt x11-proto/xf86driproto x11-misc/imake x11-misc/gccmakedep ) virtual/x11 )" RDEPEND=">=media-video/nvidia-glx-${NVIDIA_VERSION} >=media-video/nvidia-kernel-${NVIDIA_VERSION} >=x11-libs/gtk+-2 || ( ( x11-base/xorg-server x11-libs/libXt ) virtual/x11 )" </snip> *** Bug 123099 has been marked as a duplicate of this bug. *** Note the part where it says "yes, I'm running modular X". The correct resolution to this bug would therefore seem to be the addition of something matching virtual/x11-7*. There may also be something more elegant, but either way it is the lack of a compatible virtual ebuild that fulfulls the requirements of any package depending on virtual/x11. If this is not going to be done (IMO it should be done, though), please correct the dependency in the code you pasted to reflect either =virtual/x11-6.8 or <virtual/x11-7* or similar (possibly a blocker) so that people filling in the present gap in their package tree don't bother trying to build this version of nvidia-settings. (In reply to comment #3) > The correct resolution to this bug would therefore seem to be the addition of > something matching virtual/x11-7*. No, it wouldn't. > If this is not going to be done (IMO it should be done, though), please correct > the dependency in the code you pasted to reflect either =virtual/x11-6.8 or > <virtual/x11-7* or similar (possibly a blocker) No, that's wrong again, the dependencies are correct, you are doing invalid stuff with /etc/portage/profile/virtuals and/or /etc/portage/package.provided, which breaks the dependencies for you. I haven't touched either virtuals or package.provided, so by implication I'm not doing "invalid stuff" because I'm not doing "stuff". Kindly review the following howto and read on dependencies syntax before you consider reopening this bug again. http://www.gentoo.org/proj/en/desktop/x/x11/porting-modular-x-howto.xml *** Bug 125310 has been marked as a duplicate of this bug. *** (In reply to comment #1) > <snip> > DEPEND="virtual/libc > >=x11-libs/gtk+-2 > || ( ( x11-base/xorg-server > x11-libs/libXt > x11-proto/xf86driproto > x11-misc/imake > x11-misc/gccmakedep ) > virtual/x11 > )" > RDEPEND=">=media-video/nvidia-glx-${NVIDIA_VERSION} > >=media-video/nvidia-kernel-${NVIDIA_VERSION} > >=x11-libs/gtk+-2 > || ( ( x11-base/xorg-server > x11-libs/libXt ) > virtual/x11 > )" > </snip> > Since 20 March 2006 there is a virtual/x11-7.0 in portage wich makes the dependency above fail if it is installed. The virtual/x11-7.0 does not have dependencies on imake or gccmakedep so emerging nvidia-settings fails as per this bug. Maybe this bug should be reopened. (In reply to comment #8) > Since 20 March 2006 there is a virtual/x11-7.0 in portage wich makes the > dependency above fail if it is installed. Yeah, that virtual just breaks things... virtual/x11-7.0-r1 with dependencies on imake, gccmakedep and makedepend has just been released which kind of invalidates this bug report again. Sorry for bugging ;-) Fixed then *** Bug 128753 has been marked as a duplicate of this bug. *** *** Bug 130157 has been marked as a duplicate of this bug. *** *** Bug 139155 has been marked as a duplicate of this bug. *** emerge -a1 imake gccmakedep *** Bug 139645 has been marked as a duplicate of this bug. *** *** Bug 140529 has been marked as a duplicate of this bug. *** |