Zypper conflict resolution query

[ENTPRESTIGIOUS]

I can’t update to the latest snapshot because there’s a conflict between packages from Packman and from the openSUSE repositories.

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: 1: problem with the installed libOSMesa8-25.0.5-1699.415.pm.3.x86_64
Problem: 2: problem with the installed libOSMesa8-32bit-25.0.5-1699.415.pm.3.x86_64

Problem: 1: problem with the installed libOSMesa8-25.0.5-1699.415.pm.3.x86_64
 Solution 1: install libOSMesa8-25.0.5-414.1.x86_64 from vendor openSUSE
  replacing libOSMesa8-25.0.5-1699.415.pm.3.x86_64 from vendor http://packman.links2linux.de
 Solution 2: keep obsolete libOSMesa8-25.0.5-1699.415.pm.3.x86_64

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

[hui]

You as administrator of the system, need to answer the solver question. This is needed to upgrade your system.

[ENTPRESTIGIOUS]

@hui

You as administrator of the system, need to answer the solver question

Are those packages deprecated in the Packman repo?

[ENTPRESTIGIOUS]

It looks like someone is experiencing the same issue: Reddit - The heart of the internet

[deano_ferrari]

There have been a number of similar topics reported by users who have been impacted from time to time when using Mesa packages from Packman. While using the Packman versions may offer hardware-accelerated patented codecs that the default openSUSE packages can’t provide, there can be an increased risk of instability relative to the OSS packages, as the openSUSE packages go through a more rigorous testing (openQA testing framework) prior to release. Also, make sure that the Mesa packages are not mixed.

[enziosavio]

I chose solution 2 for both problems.

[kyral]

stupid question : why can’t OpenSUSE provide the hardware accelerated patented codecs, but packman can ? and why some distros like Arch don’t have this problem ? Ubuntu provides a repo with codecs, which never causes any conflics with updates, i think OpenSUSE might be the only distro i’ve seen with this strange issue

[deano_ferrari]

This has been explained many times over the years…here’s a recent discussion that covers the ground well…

Reintroduce some media codecs into official repos

With a change introduced 2 years ago, some video codecs have been excluded from the official mesa build. Specifically h264, h265/HVEC and AC-1 where disabled. Maybe more where disabled earlier or later, I’m not sure. This has caused people who value battery life and or smooth video playback to add packman-essentials repo. However it has not been uncommon for the packman mesa to end up a version behind the official mesa for one or a few days causing update conflicts, in practice preventing upd…

[gogalthorp]

Note the name openSUSE ie open software only

[OrsoBruno]

@ENTPRESTIGIOUS

Are those packages deprecated in the Packman repo?

Yes, apparently: Packman search

[arvidjaar]

@OrsoBruno

Packman search

Thu May  8 13:39:58 UTC 2025 - Stefan Dirsch

- Update to release 25.1.0
...
- osmesa no longer available; it's considered redundant with EGL
  surfaceless

@deano_ferrari

the openSUSE packages go through a more rigorous testing (openQA testing framework) prior to release

Which has nothing to do with the Packman issue(s). Packman follows Factory, not Tumbleweed, so it is ahead of Tumbleweed. OSMesa was removed in the new Mesa version in Factory which is now available in Packman, but not yet available in Tumbleweed.

[deano_ferrari]

I didn’t say it did. That’s your assumption. Mine was a general comment which is true in it’s own right. You’re reading things out of context.

[enziosavio]

However this is a small problem, just read if there is a change of supplier, and in the case of Mesa drivers, better not to mix rpm of two repositories and wait a few days before updating. I use Tumbleweed when these dependencies occur I close zypper dup and switch to Yast to check better.

[malcolmlewis]

Hi All
Remember Mesa moved to Extras repository so if only using Essentials it’s not present…?

@arvidjaar It builds against Multimedia/openSUSE_Tumbleweed these days, AFAIK it was changed…

[arvidjaar]

@malcolmlewis

It builds against Multimedia/openSUSE_Tumbleweed

What is Multimedia/openSUSE_Tumbleweed?

Anyway, if you go to Show Extra / A_tw-Mesa - Packman Build Service PMBS, you will see

And

[malcolmlewis]

@arvidjaar The repository it builds against https://pmbs.links2linux.de/projects/Extra/meta

[pallaswept]

https://bugzilla.opensuse.org/show_bug.cgi?id=1243713

[arvidjaar]

@malcolmlewis

The repository it builds against

It does not matter what it builds against. What matters is where package sources come from. Package sources for Mesa come from Factory.

[arvidjaar]

Adding unrelated information to a bug report does not help anyone.

[yoman]

@ENTPRESTIGIOUS hi

To fix this conflict between Packman and openSUSE packages, you should run :

sudo zypper dup --allow-vendor-change

This command allows Zypper to switch packages from one vendor (like Packman) to another (like openSUSE) when needed, which resolves repository conflicts during the distribution upgrade.