Since conky depends on nvidia-settings, which is 295.20 on stable arches, it tries to downgrade any existing nvidia-drivers to 295.75 as a result (because nvidia-settings depends on nvidia-drivers). The reason nvidia-settings packages are no longer made stable is because the nvidia-settings executable is part of the nvidia-drivers package, hence, dependencies on nvidia-settings should be replaced by dependencies on nvidia-drivers. # eshowkw nvidia-drivers Keywords for x11-drivers/nvidia-drivers: | | u | | a a p s | n | | l m h i m m p s p | u s | r | p d a p a 6 i p c 3 a x | s l | e | h 6 r p 6 8 p p 6 9 s r 8 | e o | p | a 4 m a 4 k s c 4 0 h c 6 | d t | o ----------+---------------------------+-----+------- 96.43.20 | * + * * * * * * * * * * + | # 0 | gentoo 96.43.23 | * + * * * * * * * * * * + | # | gentoo 173.14.35 | * + * * * * * * * * * * + | # | gentoo 173.14.36 | * + * * * * * * * * * * + | # | gentoo 295.71 | * + * * * * * * * * * * + | # | gentoo 295.75 | * + * * * * * * * * * * + | # | gentoo 304.60 | * + * * * * * * * * * * + | # | gentoo 304.64 | * + * * * * * * * * * * + | o | gentoo [I]310.19 | * ~ * * * * * * * * * * ~ | o | gentoo # eshowkw nvidia-settings Keywords for media-video/nvidia-settings: | | u | | a a p s | n | | l m h i m m p s p | u s | r | p d a p a 6 i p c 3 a x | s l | e | h 6 r p 6 8 p p 6 9 s r 8 | e o | p | a 4 m a 4 k s c 4 0 h c 6 | d t | o ----------+---------------------------+-----+------- 173.14.31 | * ~ * * * * * * * * * * ~ | # 0 | gentoo 260.19.29 | * + * * * * * * * * * * + | # | gentoo 275.43 | * ~ * * * * * * * * * * ~ | # | gentoo 290.10 | * ~ * * * * * * * * * * ~ | # | gentoo 295.20 | * + * * * * * * * * * * + | o | gentoo 295.40 | * ~ * * * * * * * * * * ~ | # | gentoo 302.11 | * ~ * * * * * * * * * * ~ | # | gentoo 304.60 | * ~ * * * * * * * * * * ~ | # | gentoo [I]310.19 | * ~ * * * * * * * * * * ~ | o | gentoo
@hardened: I tried to switch a dependency for conky from nvidia? ( media-video/nvidia-settings ) to nvidia? ( x11-drivers/nvidia-drivers[tools]). After running a repoman check I got the following QA warnings: dependency.bad 24 app-admin/conky/conky-1.9.0.ebuild: DEPEND: amd64(hardened/linux/amd64/no-multilib/selinux) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0.ebuild: RDEPEND: amd64(hardened/linux/amd64/no-multilib/selinux) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0.ebuild: DEPEND: amd64(hardened/linux/amd64/no-multilib) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0.ebuild: RDEPEND: amd64(hardened/linux/amd64/no-multilib) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0.ebuild: DEPEND: amd64(hardened/linux/amd64/selinux) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0.ebuild: RDEPEND: amd64(hardened/linux/amd64/selinux) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0.ebuild: DEPEND: amd64(hardened/linux/amd64) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0.ebuild: RDEPEND: amd64(hardened/linux/amd64) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0.ebuild: DEPEND: x86(hardened/linux/x86/selinux) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0.ebuild: RDEPEND: x86(hardened/linux/x86/selinux) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0.ebuild: DEPEND: x86(hardened/linux/x86) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0.ebuild: RDEPEND: x86(hardened/linux/x86) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0-r1.ebuild: DEPEND: amd64(hardened/linux/amd64/no-multilib/selinux) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0-r1.ebuild: RDEPEND: amd64(hardened/linux/amd64/no-multilib/selinux) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0-r1.ebuild: DEPEND: amd64(hardened/linux/amd64/no-multilib) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0-r1.ebuild: RDEPEND: amd64(hardened/linux/amd64/no-multilib) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0-r1.ebuild: DEPEND: amd64(hardened/linux/amd64/selinux) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0-r1.ebuild: RDEPEND: amd64(hardened/linux/amd64/selinux) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0-r1.ebuild: DEPEND: amd64(hardened/linux/amd64) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0-r1.ebuild: RDEPEND: amd64(hardened/linux/amd64) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0-r1.ebuild: DEPEND: x86(hardened/linux/x86/selinux) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0-r1.ebuild: RDEPEND: x86(hardened/linux/x86/selinux) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0-r1.ebuild: DEPEND: x86(hardened/linux/x86) ['x11-drivers/nvidia-drivers[tools]'] app-admin/conky/conky-1.9.0-r1.ebuild: RDEPEND: x86(hardened/linux/x86) ['x11-drivers/nvidia-drivers[tools]'] From looking at the hardened profiles I found the use flags X and tools are masked for the nvidia-drivers in package.use.ask. I guess this causes the warnings. I think masking the nvidia use flag for conky as well should fix this.
Use nvidia for app-admin/conky masked in the hardened profile.
+ 30 Nov 2012; Daniel Pielmeier <billie@gentoo.org> conky-1.9.0.ebuild, + conky-1.9.0-r1.ebuild, metadata.xml: + Depend on nvidia-drivers[tools] instead of nvidia-settings. Apparently + nvidia-settings won't become stable anymore. Thanks to Tom Wijsman for the + report and Magnus Granberg for adding the required masks in the hardened + profile.
(In reply to comment #3) > + Depend on nvidia-drivers[tools] instead of nvidia-settings. Apparently > + nvidia-settings won't become stable anymore. Thanks to Tom Wijsman for the > + report and Magnus Granberg for adding the required masks in the hardened > + profile. That's not true, see bug 443594.
@hardened: There was a communication issue. There will be stable versions of nvidia-settings and I can leave the old dependency for conky in place. This makes your mask unnecessary. My apologies.
When nvidia-settings gets stabilized, this bug can be closed as INVALID; if it does not get stabilized, we should continue with the prior approach. Did anyone already involve the maintainers of nvidia-drivers and nvidia-settings to clarify what they want to do with both packages?
(In reply to comment #6) > When nvidia-settings gets stabilized, this bug can be closed as INVALID; if > it does not get stabilized, we should continue with the prior approach. > > Did anyone already involve the maintainers of nvidia-drivers and > nvidia-settings to clarify what they want to do with both packages? I did contact the maintainer of nvidia-settings and he told me that there will be stable versions of nvidia-settings. Problem was the drivers got stabled before the settings. Hopefully this will get coordinated better in the future. I close this bug when the nvidia-drivers become stable.
Closing nvidia-settings are now stable.
