| Summary: | media-video/nvidia-settings-355.11 depends on mismatched version of x11-drivers/nvidia-drivers | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | N. Andrew Walsh <n.andrew.walsh> |
| Component: | Current packages | Assignee: | Christian Ruppert (idl0r) <idl0r> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | amd64, bfrg100, pageexec, the.paraw |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
I can confirm that. Exact same thing here. Also, I doubt it is intentional, since also the ebuild for nvidia-settings-355.11 has an RDEPEND on nvidia-drivers:0/340 rather than 0/350. also seeing this, with the added twist that upgrading gentoo settings is forcing a downgrade of my drivers: [ebuild UD ] x11-drivers/nvidia-drivers-340.93-r1:0/340::gentoo [352.21:0/0::gentoo] USE="X acpi multilib tools -pax_kernel -uvm (-gtk2%) (-gtk3%*)" 68,178 KiB [ebuild U ] media-video/nvidia-settings-355.11::gentoo [343.22::gentoo] USE="gtk3%* -examples" 1,534 KiB *upgrading nvidia-settings Sorry, that sub-slot foo has been fixed now. Please sync again in a bit and try again. It now depends upon 0/355. I'm getting the same error. This is my (partial) output of after "emerge --sync && emerge -avuDN --with-bdeps=y @world" [ebuild UD ] x11-drivers/nvidia-drivers-340.93::gentoo [352.30::gentoo] USE="X acpi multilib tools -pax_kernel -uvm* (-gtk2%*) (-gtk3%)" 68,178 KiB [ebuild U ] media-video/nvidia-settings-340.58::gentoo [331.20::gentoo] USE="-examples" 1,514 KiB |
I'm not sure if this is intentional or not, but nvidia-settings-355.11 has the following RDEPEND: RDEPEND="${COMMON_DEPEND} x11-drivers/nvidia-drivers:0/340" So, even though nvidia-drivers with a :0/350 meta exists (and is installed on my system), nvidia-settings is forcing a downgrade. Was this intentional? Is nvidia-settings supposed to force a downgrade to a lower-than-matching version? Or is that an error in the ebuild (since the :0/340 version seems to have been added to all of the nvidia-settings ebuilds)? Reproducible: Always Steps to Reproduce: 1. emerge nvidia-drivers-355.* 2. try to emerge nvidia-settings-355.* 3. fail Actual Results: humiliation and emo tears Expected Results: matching versions between -drivers and -settings?