DNF keeps trying to install weak dependency 'mesa-va-drivers' which conflicts with 'mesa-va-drivers-freeworld'

Ask Fedora
,
1

Today, for the second time, I had to tell DNF to not attempt to install weak dependencies because it tries to install a package that conflicts with an already-installed package (from RPMFusion).

Should I just set the DNF default to never install weak dependencies?

1 Like
2

Try

dnf upgrade --setopt=install_weak_deps=False

This is a modified example from man dnf.

1 Like
3

Yes, that’s what I’ve been doing, but I’ve never had to do this until the past two weeks.

4

This is being discussed here, 6426 – Review request: mesa-freeworld - Mesa graphics libraries

you should also be able to do: --exclude=mesa-va-drivers

2 Likes
5

I’m facing again this issue now with Fedora 38… is anyone else having problems?

6

Please post the exact messages you see. With F37 there was a delay in having the mesa-va-drivers-freeworld package version not matching the mesa-filesystem version. However with F38 that should not be an issue.

2 Likes
7

The packages gstreamer1-vaapi and mesa-dri-drivers recommends mesa-va-drivers(x86-64) which is provided by mesa-va-drivers but not by mesa-va-drivers-freeworld.

1 Like
8

Strange you say that.

# dnf list installed mesa*
Installed Packages
mesa-dri-drivers.x86_64                                                 23.0.2-2.fc38                                        @updates       
mesa-filesystem.x86_64                                                  23.0.2-2.fc38                                        @updates       
mesa-libEGL.x86_64                                                      23.0.2-2.fc38                                        @updates       
mesa-libEGL-devel.x86_64                                                23.0.2-2.fc38                                        @updates       
mesa-libGL.x86_64                                                       23.0.2-2.fc38                                        @updates       
mesa-libGLU.x86_64                                                      9.0.1-8.fc38                                         @fedora        
mesa-libgbm.x86_64                                                      23.0.2-2.fc38                                        @updates       
mesa-libgbm-devel.x86_64                                                23.0.2-2.fc38                                        @updates       
mesa-libglapi.x86_64                                                    23.0.2-2.fc38                                        @updates       
mesa-libxatracker.x86_64                                                23.0.2-2.fc38                                        @updates       
mesa-va-drivers-freeworld.x86_64                                        23.0.2-1.fc38                                        @rpmfusion-free
mesa-vulkan-drivers.x86_64                                              23.0.2-2.fc38                                        @updates       


# dnf list installed gstreamer1-vaapi
Installed Packages
gstreamer1-vaapi.x86_64                                                1.22.2-1.fc38                                                @updates

Note that I have mesa-dri-drivers, mesa-va-drivers-freeworld, and gstreamer1-vaapi all installed with no errors.

9

It depends on the exact version of the mesa packages. The maintainers are currently hard at work trying to fix the conflicts between the mesa packages from Fedora and the ones from Rpmfusion. So what was true last week may not be true tomorrow.

2 Likes
10

@vekruse, I still see that some mesa-va-drivers -debuginfos that coredumpctl debug requests are outdated, which prevents me generating useful traces in gnome-abrt (especially for some reproducible issues caused by bugzilla.redhat.com/show_bug.cgi?id=2381911#c0.) [1] [2]

  1. retrace.fedoraproject.org/faf/reports/1267724 ↩︎

  2. retrace.fedoraproject.org/faf/reports/1218587 ↩︎