Mesa conflicts, what to do?

[40476]

usr_40476@localhost:~> sudo zypper dup
[sudo] password for root: 
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
3 Problems:
Problem: 1: the installed Mesa-32bit-24.0.3-1699.375.pm.3.x86_64 requires 'Mesa = 24.0.3', but this requirement cannot be provided
not installable providers: Mesa-24.0.3-372.1.x86_64[https-download.opensuse.org-8c9cae55]
                   Mesa-24.0.3-372.1.x86_64[repo-oss]

Problem: 2: the installed Mesa-24.0.3-1699.375.pm.3.x86_64 requires 'Mesa-dri = 24.0.3', but this requirement cannot be provided
deleted providers: Mesa-dri-24.0.3-1699.375.pm.4.x86_64
not installable providers: Mesa-dri-24.0.3-372.2.x86_64[https-download.opensuse.org-8c9cae55]
                   Mesa-dri-24.0.3-1699.375.pm.5.i586[packman]
                   Mesa-dri-24.0.3-372.2.x86_64[repo-oss]

Problem: 3: the installed Mesa-24.0.3-1699.375.pm.3.x86_64 requires 'Mesa-gallium = 24.0.3', but this requirement cannot be provided
deleted providers: Mesa-gallium-24.0.3-1699.375.pm.4.x86_64
not installable providers: Mesa-gallium-24.0.3-372.2.x86_64[https-download.opensuse.org-8c9cae55]
                   Mesa-gallium-24.0.3-1699.375.pm.5.i586[packman]
                   Mesa-gallium-24.0.3-372.2.x86_64[repo-oss]


Problem: 1: the installed Mesa-32bit-24.0.3-1699.375.pm.3.x86_64 requires 'Mesa = 24.0.3', but this requirement cannot be provided
not installable providers: Mesa-24.0.3-372.1.x86_64[https-download.opensuse.org-8c9cae55]
                   Mesa-24.0.3-372.1.x86_64[repo-oss]

 Solution 1: install Mesa-24.0.3-372.1.x86_64 from vendor openSUSE
  replacing Mesa-24.0.3-1699.375.pm.3.x86_64 from vendor http://packman.links2linux.de
 Solution 2: deinstallation of Mesa-32bit-24.0.3-1699.375.pm.3.x86_64
 Solution 3: install Mesa-24.0.3-1699.375.pm.3.i586 despite the inferior architecture
 Solution 4: keep obsolete Mesa-24.0.3-1699.375.pm.3.x86_64
 Solution 5: break Mesa-32bit-24.0.3-1699.375.pm.3.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/4/5/s/r/c/d/?] (c): 

[malcolmlewis]

@40476 Different day, same issue… Packman Tumbleweed is linked to Factory which has built 24.0.5 before it’s released in a Tumbleweed snapshot… don’t use packman, or wait a few days…

[karlmistelberger]

Infamous host erlangen uses the packman repo. Daily dist-upgrades never run into conflicts caused by the repo:

Noninteractive System Upgrades

Vendor configuration defaults of zypper are very conservative. Astute users may want to tweak solver default settings and some more options: 3400g:~ # grep ^solver /etc/zypp/zypp.conf solver.onlyRequires = true solver.allowVendorChange = true solver.dupAllowVendorChange = true solver.cleandepsOnRemove = true 3400g:~ # Use of priorities allows for safe non-interactive operation: https://www.youtube.com/watch?v=x8kEaJU6hlw 3400g:~ # zypper repos --alias --uri --refresh --show-enabled-only…

[pavinjoseph]

There are a few caveats to this approach, dup would succeed with modified solver config but for the short period when Mesa packages are mixed from both Packman and openSUSE it might cause weird issues such as Wayland session not being available.

[karlmistelberger]

@pavinjoseph

for the short period when Mesa packages are mixed from both Packman and openSUSE it might cause weird issues such as Wayland session not being available.

I don’t think so:

erlangen:~ # zypper search  --details --installed-only Mesa
Loading repository data...
Reading installed packages...

S  | Name                      | Type    | Version              | Arch   | Repository
---+---------------------------+---------+----------------------+--------+-----------------------
i+ | Mesa                      | package | 24.0.5-1699.376.pm.1 | x86_64 | Packman
i+ | Mesa-demo-x               | package | 9.0.0-3.3            | x86_64 | Haupt-Repository (OSS)
i+ | Mesa-dri                  | package | 24.0.5-1699.376.pm.1 | x86_64 | Packman
i+ | Mesa-gallium              | package | 24.0.5-1699.376.pm.1 | x86_64 | Packman
i+ | Mesa-libEGL1              | package | 24.0.5-1699.376.pm.1 | x86_64 | Packman
i+ | Mesa-libGL1               | package | 24.0.5-1699.376.pm.1 | x86_64 | Packman
i+ | Mesa-libglapi0            | package | 24.0.5-1699.376.pm.1 | x86_64 | Packman
i+ | Mesa-libva                | package | 24.0.5-1699.376.pm.1 | x86_64 | Packman
i+ | Mesa-vulkan-device-select | package | 24.0.5-1699.376.pm.1 | x86_64 | Packman
erlangen:~ # 

Available logs show each package upgrades smoothly without further ado:

erlangen:~ # journalctl -q -u dup -g 'Installing: Mesa-24.0'
Apr 05 08:00:40 erlangen zypper[16416]: ( 7/15) Installing: Mesa-24.0.3-1699.373.pm.1.x86_64 [...done]
Apr 06 14:28:59 erlangen zypper[1603]: (3068/3903) Installing: Mesa-24.0.3-1699.373.pm.1.x86_64 [...done]
Apr 09 20:24:03 erlangen zypper[16976]: (13/15) Installing: Mesa-24.0.3-1699.375.pm.1.x86_64 [...done]
Apr 12 12:40:05 erlangen zypper[1311]: (27/47) Installing: Mesa-24.0.3-1699.375.pm.2.x86_64 [...done]
Apr 19 01:14:15 erlangen zypper[16129]: (39/67) Installing: Mesa-24.0.3-1699.375.pm.3.x86_64 [...done]
Apr 25 05:11:01 erlangen zypper[22070]: (22/39) Installing: Mesa-24.0.5-1699.376.pm.1.x86_64 [...done]
erlangen:~ # 

1. Packman higher priority makes sure packages are installed from this repo only.

2. If upgrading would result in conflicts zypper would opt for keeping the current versions.

3. If keeping current versions would result in conflicts too zypper would give up. This happens on very rare occasions only.

[pavinjoseph]

@karlmistelberger

Packman higher priority makes sure packages are installed from this repo only.

Does zypper not choose the highest version from the lower priority openSUSE repos when it’s available? This was what caused the issues for me when Packman was a bit slow in rolling out updates.

[kill_it]

Confirm. Upgrading Mesa-dri to 24.0.5 from Packman breaks Wayland.

[karlmistelberger]

@pavinjoseph

Does zypper not choose the highest version from the lower priority openSUSE repos when it’s available?

A higher version exists:

erlangen:~ # zypper search --details --match-exact librist4.x86_64
Loading repository data...
Reading installed packages...

S  | Name     | Type    | Version            | Arch   | Repository
---+----------+---------+--------------------+--------+-----------------------
i+ | librist4 | package | 0.2.7-1699.1.pm.22 | x86_64 | Packman
v  | librist4 | package | 0.2.10-1.3         | x86_64 | Haupt-Repository (OSS)
erlangen:~ # 

Packman high priority 90:

erlangen:~ # zypper -n dup -dD
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
Nothing to do.
erlangen:~ # 

Packman default priority 99:

erlangen:~ # zypper -n dup -dD
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...

The following package is going to be upgraded:
  librist4

The following package is going to change vendor:
  librist4  http://packman.links2linux.de -> openSUSE

1 package to upgrade, 1 to change vendor.
Overall download size: 0 B. Already cached: 108.5 KiB. Download only.

Backend:  classic_rpmtrans --dry-run --download-only
Continue? [y/n/v/...? shows all options] (y): y
In cache librist4-0.2.10-1.3.x86_64.rpm                                                                                                                                                                                 (1/1), 108.5 KiB    

Checking for file conflicts: .........................................................................................................................................................................................................[done]
erlangen:~ # 

[karlmistelberger]

@kill_it

Upgrading Mesa-dri to 24.0.5 from Packman breaks Wayland.

Infamous host erlangen has installed:

erlangen:~ # zypper search  --details --installed-only Mesa-dri
Loading repository data...
Reading installed packages...

S  | Name     | Type    | Version              | Arch   | Repository
---+----------+---------+----------------------+--------+-----------
i+ | Mesa-dri | package | 24.0.5-1699.376.pm.1 | x86_64 | Packman
erlangen:~ # 

Wayland works! Presumably you missed some subtleties.

From https://en.opensuse.org/Portal:Tumbleweed: “Note that there can be some subtleties with updates, especially with multiple repositories. See for example recent discussion about using zypper dup versus zypper up and zypper dup priorities.”

[kill_it]

Wayland works!

what is your GPU?

Presumably you missed some subtleties.

Definitely it complains on DRM module version mismatch.

[malcolmlewis]

@karlmistelberger So lets see what 32bit Mesa packages you have installed, which is the original posters issue?

Please note, what works for one person doesn’t work for others. Focus on the users issue, not whether it works for you or not, using whatever method works for you.