Mesa Conflict (Packman vs OpenSUSE)

English Applications
1

Following my attempt to execute ‘zypper dup’ today in Tumbleweed, I encountered the following conflict. It appears that I have a newer repository installed from ‘opi codecs’ compared to the incoming upgrade (OpenSUSE). I’m unsure if this issue will resolve itself given enough time or if there’s a current workaround. I understand that one solution could be to remove Mesa and replace it with the OpenSUSE version, but that would also remove the installed codec support via ‘opi’. Any assistance in navigating this situation would be greatly appreciated. Thank you.

abystus@abystus-pc: ~ $ sudo zypper dup
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...
2 Problems:
Problem: nothing provides 'Mesa-dri-32bit = 24.0.3' needed by the to be installed Mesa-32bit-24.0.3-1699.371.pm.1.x86_64
Problem: nothing provides 'Mesa-dri-32bit = 24.0.3' needed by the to be installed Mesa-32bit-24.0.3-1699.371.pm.1.x86_64

Problem: nothing provides 'Mesa-dri-32bit = 24.0.3' needed by the to be installed Mesa-32bit-24.0.3-1699.371.pm.1.x86_64
 Solution 1: deinstallation of Mesa-32bit-23.3.6-1699.370.pm.1.x86_64
 Solution 2: keep obsolete Mesa-32bit-23.3.6-1699.370.pm.1.x86_64
 Solution 3: break Mesa-32bit-24.0.3-1699.371.pm.1.x86_64 by ignoring some of its dependencies

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

Problem: nothing provides 'Mesa-dri-32bit = 24.0.3' needed by the to be installed Mesa-32bit-24.0.3-1699.371.pm.1.x86_64
 Solution 1: deinstallation of Mesa-libGL1-32bit-23.3.6-1699.370.pm.1.x86_64
 Solution 2: keep obsolete Mesa-libGL1-32bit-23.3.6-1699.370.pm.1.x86_64
 Solution 3: break Mesa-32bit-24.0.3-1699.371.pm.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): 2
Resolving dependencies...
Computing distribution upgrade...
4 Problems:
Problem: the installed Mesa-32bit-23.3.6-1699.370.pm.1.x86_64 requires 'Mesa = 23.3.6', but this requirement cannot be provided
Problem: nothing provides 'Mesa-dri-32bit = 24.0.3' needed by the to be installed Mesa-32bit-24.0.3-1699.371.pm.1.x86_64
Problem: the installed Mesa-libGL1-32bit-23.3.6-1699.370.pm.1.x86_64 requires 'Mesa-32bit = 23.3.6', but this requirement cannot be provided
Problem: nothing provides 'Mesa-dri-32bit = 24.0.3' needed by the to be installed Mesa-32bit-24.0.3-1699.371.pm.1.x86_64

Problem: the installed Mesa-32bit-23.3.6-1699.370.pm.1.x86_64 requires 'Mesa = 23.3.6', but this requirement cannot be provided
  deleted providers: Mesa-23.3.6-1699.370.pm.1.x86_64
not installable providers: Mesa-23.3.6-369.1.x86_64[download.opensuse.org-oss]
 Solution 1: install Mesa-23.3.6-369.1.x86_64 from vendor openSUSE
  replacing Mesa-23.3.6-1699.370.pm.1.x86_64 from vendor http://packman.links2linux.de
 Solution 2: keep obsolete Mesa-23.3.6-1699.370.pm.1.x86_64
 Solution 3: remove lock to allow removal of Mesa-32bit-23.3.6-1699.370.pm.1.x86_64
 Solution 4: break Mesa-32bit-23.3.6-1699.370.pm.1.x86_64 by ignoring some of its dependencies

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

Problem: nothing provides 'Mesa-dri-32bit = 24.0.3' needed by the to be installed Mesa-32bit-24.0.3-1699.371.pm.1.x86_64
 Solution 1: deinstallation of Mesa-32bit-23.3.6-1699.370.pm.1.x86_64
 Solution 2: install Mesa-dri-23.3.6-369.1.x86_64 from vendor openSUSE
  replacing Mesa-dri-23.3.6-1699.370.pm.2.x86_64 from vendor http://packman.links2linux.de
 Solution 3: install Mesa-dri-23.3.6-1699.370.pm.2.i586 despite the inferior architecture
 Solution 4: keep obsolete Mesa-dri-23.3.6-1699.370.pm.2.x86_64
 Solution 5: break Mesa-32bit-24.0.3-1699.371.pm.1.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): 4

Problem: the installed Mesa-libGL1-32bit-23.3.6-1699.370.pm.1.x86_64 requires 'Mesa-32bit = 23.3.6', but this requirement cannot be provided
  deleted providers: Mesa-32bit-23.3.6-1699.370.pm.1.x86_64
not installable providers: Mesa-32bit-23.3.6-369.1.x86_64[download.opensuse.org-oss]
 Solution 1: install Mesa-gallium-23.3.6-369.1.x86_64 from vendor openSUSE
  replacing Mesa-gallium-23.3.6-1699.370.pm.2.x86_64 from vendor http://packman.links2linux.de
 Solution 2: install Mesa-gallium-23.3.6-1699.370.pm.2.i586 despite the inferior architecture
 Solution 3: keep obsolete Mesa-gallium-23.3.6-1699.370.pm.2.x86_64
 Solution 4: remove lock to allow removal of Mesa-libGL1-32bit-23.3.6-1699.370.pm.1.x86_64
 Solution 5: break Mesa-libGL1-32bit-23.3.6-1699.370.pm.1.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): 3

Problem: nothing provides 'Mesa-dri-32bit = 24.0.3' needed by the to be installed Mesa-32bit-24.0.3-1699.371.pm.1.x86_64
 Solution 1: install Mesa-libEGL1-23.3.6-369.1.x86_64 from vendor openSUSE
  replacing Mesa-libEGL1-23.3.6-1699.370.pm.1.x86_64 from vendor http://packman.links2linux.de
 Solution 2: deinstallation of Mesa-libGL1-32bit-23.3.6-1699.370.pm.1.x86_64
 Solution 3: keep obsolete Mesa-libEGL1-23.3.6-1699.370.pm.1.x86_64
 Solution 4: break Mesa-32bit-24.0.3-1699.371.pm.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c/d/?] (c): 3
Resolving dependencies...
Computing distribution upgrade...

Problem: the to be installed Mesa-libGL1-24.0.3-1699.371.pm.1.x86_64 requires 'Mesa = 24.0.3', but this requirement cannot be provided
  not installable providers: Mesa-24.0.3-1699.371.pm.1.i586[packman]
                   Mesa-24.0.3-1699.371.pm.1.x86_64[packman]
 Solution 1: Following actions will be done:
  remove lock to allow removal of Mesa-23.3.6-1699.370.pm.1.x86_64
  remove lock to allow removal of Mesa-dri-23.3.6-1699.370.pm.2.x86_64
  remove lock to allow removal of Mesa-32bit-23.3.6-1699.370.pm.1.x86_64
  remove lock to allow removal of Mesa-libGL1-32bit-23.3.6-1699.370.pm.1.x86_64
 Solution 2: install Mesa-libGL1-23.3.6-369.1.x86_64 from vendor openSUSE
  replacing Mesa-libGL1-23.3.6-1699.370.pm.1.x86_64 from vendor http://packman.links2linux.de
 Solution 3: keep obsolete Mesa-libGL1-23.3.6-1699.370.pm.1.x86_64
 Solution 4: break Mesa-libGL1-24.0.3-1699.371.pm.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c): 3
Resolving dependencies...
Computing distribution upgrade...

The following 7 items are locked and will not be changed by any action:
 Installed:
  Mesa Mesa-32bit Mesa-dri Mesa-gallium Mesa-libEGL1 Mesa-libGL1 Mesa-libGL1-32bit

The following 33 packages are going to be upgraded:
  ffmpeg-6 gstreamer-plugins-bad-codecs gstreamer-plugins-ugly-codecs libavcodec60 libavdevice60 libavfilter9 libavformat60 libavutil58
  libfdk-aac2 libfdk-aac2-32bit libgbm1 libOSMesa8 libOSMesa8-32bit libpostproc57 libswresample4 libswscale7 libvdpau_r600
  libvdpau_radeonsi libvlc5 libvlccore9 libvulkan_intel libvulkan_radeon Mesa-libglapi0 Mesa-libglapi0-32bit Mesa-libva
  Mesa-vulkan-device-select vlc vlc-codec-gstreamer vlc-codecs vlc-lang vlc-noX vlc-qt vlc-vdpau

33 packages to upgrade.
Overall download size: 0 B. Already cached: 49.0 MiB. After the operation, additional 3.6 MiB will be used.
Continue? [y/n/v/...? shows all options] (y):
2

If you lock packages you are expected to understand what you did and the consequences of it. You told zypper to not change some packages and now you are surprised that it breaks dependencies when these packages were replaced by new versions?

If you have reasons to add lock, you probably do not want to change existing packages so need to select “keep” and add more locks to avoid these errors from zypper. Otherwise you need to remove lock and try again.

3

Out of the wall of text I posted, you found the only thing that wasn’t the problem. I know the packages are locked, but that isn’t the issue that the thread was created for.

I assume you intentionally skipped over the following in a rush to find the “user” error:

2 Problems:
Problem: nothing provides 'Mesa-dri-32bit = 24.0.3' needed by the to be installed Mesa-32bit-24.0.3-1699.371.pm.1.x86_64
Problem: nothing provides 'Mesa-dri-32bit = 24.0.3' needed by the to be installed Mesa-32bit-24.0.3-1699.371.pm.1.x86_64

As another post has already pointed out, holding off on the update for now is most likely the solution, and if not it can always be uninstalled and replaced with the openSUSE variant sans codecs.

4

Packman user shouldn‘t ask that regularly for obvious solutions for expected hiccups.
It is a 3rd party repo which regularly breaks :tipping_hand_man:

5

The only reason it is being used is for codec support. I assume anyone using openSUSE as a desktop uses Packman repos for codecs. Is there a more efficient way to get codecs without the inherent breakage of Packman packages?

7 Likes
6

Mesa 24.0.3 have hit Packman repos but not yet hit tumbleweed repos so this is why it’s conflicting. It should be solved once 24.0.3 hits the tumbleweed repos in the near future.

2 Likes
7

@shorberg this issue arises all the time with third party repositories, the bulk of Packman packages are just rebuilds with flags set to allow things that openSUSE does not for Legal/Patent reasons.

So, at present using Mesa (as a Very :wink: common example);
For openSUSE;
Mesa openSUSE Development repo → openSUSE:Factory (staging) → openQA → released → openSUSE Tumbleweed repo and sync with mirrors → end users

For Packman;
Mesa openSUSE Development repo → openSUSE:Factory (staging) → Packman build/release/sync with mirrors → end users.

So as can be seen it quickly gets out of sync depending on openQA and the openSUSE Release Manager.

Problem, since Packman is a third party private (and funded) instance with limited hardware which ever way it goes end users are affected, if Mesa was linked to the release of a Tumbleweed snapshot, time is then needed for building/release to take place, so then your at the other end of the scale so to speak, especially if there are hardware/software issues (it happens more often that not) if workers are un-available, publisher stops etc…

8

I dunno why people in here got so annoyed by this. Even long time forum veterans where just out there for Packman users today.

You could have just said : “We missed something during build on packman … it will be fixed tomorrow, please dont update until then”.

But instead we got people straight up insulting people for using a suggested repo so they can consume media on their desktop pc’s.

Must have been a wild day at the office.

6 Likes
9

@Teroh not sure what you mean, the openSUSE project has no say over what happens on third party repositories?

1 Like
10

I don’t think that was the point of their post. The point trying to be made, is that ‘certain’ forum veterans could have just told the OP to hold off on the upgrade instead of giving a ridicule lecture(being rude) of what happens with certain 3rd party(Packman).

Anyway, my personal solution was to simply switch vendors to OpenSuse and install the downgraded versions, and wait until the newest version becomes available and make the jump when it does. It did not break or effect the performance of the system or anything else.

Both are effective solutions.

4 Likes
11

And just for posterity, this issue was solved by just waiting for the next release, no user action needed.

2 Likes
12

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.