File conflict upgrading to 20240111-0

English Install/Boot/Login
1

These are the conflicts:
File /usr/lib64/gstreamer-1.0/libgstasf.so
from install of
gstreamer-plugins-ugly-1.22.8-1.1.x86_64 (Main Repository (OSS))
conflicts with file from package
gstreamer-plugins-ugly-codecs-1.22.5-1699.1.pm.1.x86_64 (@System)

File /usr/lib64/gstreamer-1.0/libgstresindvd.so
from install of
gstreamer-plugins-bad-1.22.8-2.1.x86_64 (Main Repository (OSS))
conflicts with file from package
gstreamer-plugins-bad-codecs-1.22.5-1699.1.pm.1.x86_64 (@System)

File /usr/lib64/gstreamer-1.0/libgstsiren.so
from install of
gstreamer-plugins-bad-1.22.8-2.1.x86_64 (Main Repository (OSS))
conflicts with file from package
gstreamer-plugins-bad-codecs-1.22.5-1699.1.pm.1.x86_64 (@System)

Any advice on how to resolve this?

2

You have packman enabled for codecs, and I’m assuming that you never ran zypper dup --from packman so the vendoring priorities never got set.

Or you’re running zypper dup --allow-vendor-change

So what’s happening, is zypper is attempting replace the installed packman packages, with the ones from the openSUSE-OSS repo.

So it depends on what you want to do.

A) Use Packman:
run zypper dup --from packman

B) Use the OSS repo
just run zypper dup and tell it to replace those packages.

3

@lavadrop (@System) and the “pm” in the version number indicates that a) files are from Packman and b) either the Packman repo has been removed, or disabled…

But what @sfalken says is correct (if the repo is re-added or enabled…)

4

I would note the --from packman bit, assumes that the repo is enabled, and called “packman” yes.

doing zypper lr will tell you what the “short names” for all your repositories are.

5

Thank you and yes, your second assumption is correct, this system used the radv drivers when it was running on the APU but now it also has an Intel Arc GPU and to avoid the hassle of packman conflicts I removed the repository and I thought I had changed those packages to the OSS ones.
How can I tell zypper to change all the remaining packman packages to the official ones?

6

@lavadrop I would guess that zypper -vvv dup --allow-vendor-change should get it sorted…

1 Like
7

Unfortunately it didn’t; same conflict, OSS repository conflicts with @System repository which I’ve read is what happens when packman packages are orphaned, correct?

8

@lavadrop is there an option to let the new packages overwrite?

9

There was a prompt to resolve a dependency issue about libxvidcore4 conflicting with the OSS version but with the—allow-vendor-change flag that one package and it’s 32bit version is the only vendor change. It does not register a vendor change with the gstreamer codecs bad or ugly which are causing the conflict.

10

Uninstall the packages from packman:

sudo zypper rm gstreamer-plugins-ugly-codecs gstreamer-plugins-bad-codecs gstreamer-plugins-bad-codecs

Install the packages from OSS:

sudo zypper in gstreamer-plugins-ugly gstreamer-plugins-bad gstreamer-plugins-bad`
11

In this case if it’s me I will add again the packman repository and answer the zypper file conflict one by one. You can always exit if your choices didn’t satisfy zypper dependency issue and do another try. When in doubt halt the zypper dup and wait another time and see if issues are already resolve in the next snapshot.

12

Thank you, I thought about removing them too but wanted to make sure I could resolve the rest of the orphaned packages. I guess I’ll just have to remove and add them as the conflicts show up in the future.

13

Thanks for the suggestion but no, I 'd rather not deal with packman unless absolutely necessary and since intel-media-codecs supports hardware decoding I no longer need Mesa from packman.