Ebuilds of media-video/nvidia-settings currently depend on =x11-drivers/nvidia-drivers-3*. This is one of the only two instances in the tree where the * operator is used to match a string prefix (and not a range of version components). See discussion in bug 560466 and in the -dev ML. Please consider updating the dependency such that it doesn't use * to match a part of a version component. (Maybe >=x11-drivers/nvidia-drivers-300 would be possible?)
Or maybe x11-drivers/nvidia-drivers should use subslots, if its ABI changed between versions. CCing nvidia-drivers' maintainer.
The nvidia-settings dependency is simply broken with portage-2.2.21: # emerge -av nvidia-settings These are the packages that would be merged, in order: Calculating dependencies... done! emerge: there are no ebuilds to satisfy "=x11-drivers/nvidia-drivers-3*". (dependency required by "media-video/nvidia-settings-343.22::gentoo" [ebuild]) (dependency required by "nvidia-settings" [argument]) @maintainer or qa team, please fix this now.
based on https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-drivers/nvidia-drivers/?hideattic=0 I have set the dep to be >= the oldest 3* version that was ever in gentoo. maintainer, please feel free to change this in any way you see fit that doesn't reproduce the issue with newer versions of portage.
(In reply to Rick Farina (Zero_Chaos) from comment #3) > based on > https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-drivers/nvidia- > drivers/?hideattic=0 I have set the dep to be >= the oldest 3* version that > was ever in gentoo. maintainer, please feel free to change this in any way > you see fit that doesn't reproduce the issue with newer versions of portage. Well, that's just wrong.
I have introduced sub-SLOTs on x11-drivers/nvidia-drivers and added an appropriate dependency in the remaining version of media-video/nvidia-settings. Hopefully this will encourage media-video/nvidia-settings maintainers to adhere to the branching Nvidia uses to distinguish support for different hardware in different major versions of x11-drivers-/nvidia-drivers.
I think whats happening is related to this change. So, nvidia-settings-343.22 got removed from the portage tree, https://github.com/gentoo/gentoo/commit/8c909902c0bb2fa2efedb0d7d8bb32eefe4771e6 and it had RDEPEND for >=x11-drivers/nvidia-drivers-302.17 while the currently only remaining ebuild has RDEPEND for x11-drivers/nvidia-drivers:0/340 Now I have nvidia-drivers-355.11 installed so no matter what I do it wants to downgrade them. Is this intentional? Are the later nvidia-settings uncompatible with never -drivers, and why the newer ebuild got removed? I'd like to avoid downgrading nvidia-drivers without a good reason... I tried running -1a --nodeps nvidia-settings, which installed the older version, and blocking <nvidia-drivers-355.11 but it keeps wanting to downgrade them. Im running on ~amd64.
(In reply to Jeroen Roovers from comment #4) > (In reply to Rick Farina (Zero_Chaos) from comment #3) > > based on > > https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-drivers/nvidia- > > drivers/?hideattic=0 I have set the dep to be >= the oldest 3* version that > > was ever in gentoo. maintainer, please feel free to change this in any way > > you see fit that doesn't reproduce the issue with newer versions of portage. > > Well, that's just wrong. It matches the original as closely as possible. Perhaps instead of just reporting that it is somehow wrong you could choose to elaborate in the future?
Why does nvidia-settings require specific subslots of nvidia-drivers though? This requires nvidia-settings to bump in sync with nvidia-drivers, and for example currently you cant install nvidia-settings with latest nvidia drivers (x11-drivers/nvidia-drivers-358.09:0/358::gentoo). This is wrong since I currently run these drivers fine with nvidia-settings-343.22 and I'm pretty sure I have run out of sync drivers-settings versions in the past.
So in my uninformed opinion one of these 3 needs to happen: 1)nvidia-drivers and nvidia-settings get bumped in sync by the same maintainer 2)nvidia-settings dependencies gets lax as before allowing for some breakage 3)nvidia-settings ebuild merges with drivers as per bug #562910 and people use nvidia-drivers[tools] when they want nvidia-settings
