Zypper dup file conficts

Hi,
went to do a zypper dup today but got 3 file conflicts. Two are related to gstreamer which I thought was resolved last year with a vendor change. Not sure about the /usr/bin/bitmap conflict.

Shall I just go ahead and continue?
Thanks.

Detected 3 file conflicts:

File /usr/bin/bitmap
  from install of
     Mesa-demo-8.5.0-3.1.x86_64 (openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     bitmap-1.1.0-1.5.x86_64 (@System)

File /usr/lib/gstreamer-1.0/libgstamrnb.so
  from install of
     gstreamer-plugins-ugly-32bit-1.22.1-2.1.x86_64 (openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     gstreamer-plugins-ugly-orig-addon-32bit-1.18.5-5.6.x86_64 (@System)

File /usr/lib/gstreamer-1.0/libgstamrwbdec.so
  from install of
     gstreamer-plugins-ugly-32bit-1.22.1-2.1.x86_64 (openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     gstreamer-plugins-ugly-orig-addon-32bit-1.18.5-5.6.x86_64 (@System)

File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.
Continue? [yes/no] (no): 

This package does not exist in openSUSE or Packman repo anymore. So uninstall it…

gstreamer-plugins-ugly-orig-addon-32bit

Thank you. That fixed the gstreamer part but not the bitmap issue. I did a rpm in the current package and it doesn’t have /usr/bin/bitmap

chris@asus-roc:~>$rpm -qli Mesa-demo | grep -i bitmap
/usr/lib64/mesa-demos/glsl/bitmap
/usr/lib64/mesa-demos/samples/bitmap1
/usr/lib64/mesa-demos/samples/bitmap2
/usr/lib64/mesa-demos/tests/zbitmap
chris@asus-roc:~>$

By the way - what is the @System repo? It seems to be the same(ish) as openSUSE-Tumbleweed-Oss repo.

The version currently installed does not, the updated version does.

Packages installed on your system but not present in any defined repository (exact version/vendor, not just name) are shown as @System repository. Show

zypper se -sx bitmap
chris@asus-roc:~>$zypper se -sx bitmap
Loading repository data...
Reading installed packages...

S  | Name   | Type       | Version   | Arch   | Repository
---+--------+------------+-----------+--------+---------------------------
i+ | bitmap | package    | 1.1.0-1.5 | x86_64 | openSUSE-Tumbleweed-Oss
   | bitmap | srcpackage | 1.1.0-1.5 | noarch | openSUSE-Tumbleweed-Source
chris@asus-roc:~>$

So package listed in a defined repo should be ok to overwrite one from @System?

OK, I think in this case it is just a way for zypper to say “installed package”. All installed packages are located in virtual @System repository. Saying “with the file from installed package” would be more clear.

So I let Mesa-demo-8.5.0-3.1.x86_64 be installed?

Do you really need this package? Anyway, it is up to you what to keep.

The program 'bitmap' can be found in following packages:
  * Mesa-demo [ path: /usr/bin/bitmap, repository: zypp (repo-oss) ]
  * bitmap [ path: /usr/bin/bitmap, repository: zypp (repo-oss) ]

You may consider bug report about this conflict.

I guess not if it’s just a demo thing. It must have been installed automatically ages ago.
Will consider bugzilla if it goes pear shaped.

Thanks.