[gentoo-user] gui-libs/egl-wayland and x11-drivers/nvidia-drivers dependency conflict.

Discussion:

(too old to reply)

Peter Humphrey

2024-02-17 17:40:01 UTC

Howdy,
I posted about this once before but also included pipewire and others.
We addressed the other problems but this wasn't really fixed it would
seem. I found the old thread. This is what I get today.
WARNING: One or more updates/rebuilds have been skipped due to a
gui-libs/egl-wayland:0
(gui-libs/egl-wayland-1.1.13:0/0::gentoo, ebuild scheduled for merge)
USE="" ABI_X86="(64)" conflicts with
~gui-libs/egl-wayland-1.1.7 required by
(x11-drivers/nvidia-drivers-470.223.02:0/470::gentoo, installed) USE="X
modules strip tools wayland -dist-kernel -modules-compress -modules-sign
-persistenced -static-libs" ABI_X86="(64) -32"
^ ^^^^^
I do this in a Konsole and I tried changing the fonts. The little ^^^^
things still point to places there is nothing or other wrong places.

The ^ points to the ~ character above it, and the ^^^^^ points to 1.1.7, the
version of egl-wayland, so the version you want to merge won't satisfy
nvidia-drivers.

Does that help?

--
Regards,
Peter.

Nuno Silva

2024-02-17 17:50:01 UTC

Permalink

Post by Peter Humphrey

The ^ points to the ~ character above it, and the ^^^^^ points to 1.1.7, the
version of egl-wayland, so the version you want to merge won't satisfy
nvidia-drivers.
Does that help?

Is there a setting or some other way to configure portage to use
e.g. standout mode here, instead of "^"s?

--
Nuno Silva

Dale

2024-02-17 18:00:01 UTC

Permalink

Post by Peter Humphrey

The ^ points to the ~ character above it, and the ^^^^^ points to 1.1.7, the
version of egl-wayland, so the version you want to merge won't satisfy
nvidia-drivers.
Does that help?

That's my thinking as well. Sometimes tho decoding the output of emerge
can be tricky and isn't always obvious. After I hit send for the
original message, I tried masking the new version of the egl package.
It gave a clean upgrade path BUT that package isn't up to date, just as
up to date as it can be at the moment. ;-)

Do you think this is a bug or anything else that may come to mind? I
even wonder if my video card is old enough that it is losing support. I
thought of getting a newer video card but other than being newer, I
really don't need any better since I don't do anything that puts a load
on the card I have. I check the power setting and most of the time, it
is on level 0 or level 1 if I'm watching something in 1080p on TV. It
rarely goes to full power, level 2. Even the fan generally sits at 40%
RPM. Which reminds me, I need to give that thing a blowing out. Those
things catch dust bunnies. :/

After getting that pipewire and friends problem solved, I'm getting
close to some pretty easy updates. :-D

Dale

:-) :-)

P. S. This list is a lot quieter than it used to be. The emerge
command and its friends are just getting better and better. It can work
out a update path in most all cases, even when we give it some really
bad options. Hats off to the devs. :-D :-D

Dale

2024-02-18 05:30:02 UTC

Permalink

While at it. Unrelated really but why not. Why does genlop -c show two
running for this?

(chroot) ***@fireball / # genlop -c

Currently merging 200 out of 257

* dev-qt/qtwebengine-5.15.12_p20240122

       current merge time: 1 hour, 22 minutes and 33 seconds.
       ETA: 4 hours, 58 minutes and 39 seconds.

Currently merging 200 out of 257

* dev-qt/qtwebengine-5.15.12_p20240122

       current merge time: 1 hour, 22 minutes and 34 seconds.
       ETA: 4 hours, 58 minutes and 38 seconds.
(chroot) ***@fireball / #

I notice there is a slot for version 6 and when it was compiling, it
showed only one in the list like below. However, slot 5 always shows
there is two running like above. I've never seen it do this with any
other package, large or small. It only does it with slot 5 version of
qtwebengine. This is slot 6 from earlier.

(chroot) ***@fireball / # genlop -c

Currently merging 195 out of 257

* dev-qt/qtwebengine-6.6.2

       current merge time: 2 hours, 59 minutes and 44 seconds.
       ETA: 3 hours, 21 minutes and 28 seconds.
(chroot) ***@fireball / #

By the way, that time isn't exactly right. It takes a while but not
that long. Anyone else see this? It's done this for a good while.
Just kinda weird. o_O

Dale

:-) :-)

Arve Barsnes

2024-02-17 18:00:02 UTC

Permalink

Is there a proper long term fix for this or do I need to mask the egl
package until things catch up? As long as things work, I'm fine with
masking and waiting. I just figure there may be a better fix I'm
missing. Maybe someone else sees it.

Others already answered about the arrows and the meaning of them, but
I just wanted to chime in and say that there's no reason to mask
anything at the moment, it is just a warning from portage that it
can't upgrade egl-wayland because nvidia-drivers requires the older
version. If the drivers are ever updated to allow for newer
egl-wayland, any masks would just make the upgrade more of a chore.

Regards,
Arve

Dale

2024-02-17 18:10:01 UTC

Permalink

Post by Arve Barsnes

Usually when I mask something that I hope is a temporary thing, I remove
or comment out the mask after the update is done. That way it pops back
up on the next upgrade. I sometimes put a note with it as well. My
memory isn't that great. By next week, I'll be like 'egl what'??? :/
That note reminds me. Gives my old brain a clue. LOL

It may be a while before those old drivers get updated. Those old cards
don't get much attention.

Thanks for the info tho. It helps.

Dale

:-) :-)