File conflict when update. Unsure what to do

English Install/Boot/Login
#1 
Checking for file conflicts: ..........................................................................................................................................................[error]
Detected 1 file conflict:

File /usr/lib64/sasl2/libkdexoauth2.so.3.0.0
  from install of
     sasl2-kdexoauth2-18.08.1-2.1.x86_64 (openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     sasl2-kdexoauth2-3-18.08.1-1.1.x86_64 (@System)

I am unsure how to proceed, I never had this happen before & there is a huge difference in versions. Any help is appreciated.
Thanks
JOhn

#2

In this case, just say “yes”.

And check the earlier thread: https://forums.opensuse.org/showthread.php/533339-Detected-1-file-conflict-File-usr-lib64-sasl2-libkdexoauth2-so-3-0-0-from-install-of

#3

Maybe a more general reply.

Fortunately, these file conflicts are infrequent.

When I run into one of them, I have to make a decision. Sometimes, I can see it is not important. At other times, I do some checking of the mentioned packages with Yast software management.

Usually, I want the newer version. But perhaps I want to remove the older package to avoid a possible conflict.

#4

Unfortunately I have not just this one but 32 file conflicts:

Detected 32 file conflicts:

File /usr/lib64/sasl2/libkdexoauth2.so.3.0.0
  from install of
     sasl2-kdexoauth2-18.08.1-2.1.x86_64 (openSUSE:Factory)
  conflicts with file from package
     sasl2-kdexoauth2-3-18.08.1-1.1.x86_64 (@System)

File /usr/share/locale/ar/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/ca/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/cs/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/da/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/de/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/en_CA/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/en_GB/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/es/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/es_ES/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/fa/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/fi/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/fr/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/he/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/hu/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/id/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/it/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/ja/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/ko/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/nb/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/nn_NO/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/pl/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/pt_BR/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/ro/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/ru/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/sk/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/sl/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/sv/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/tr/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/uk/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/zh_CN/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

File /usr/share/locale/zh_TW/LC_MESSAGES/libmypaint.mo
  from install of
     libmypaint-1.3.0-26.7.x86_64 (home:Herbster0815)
  conflicts with file from package
     libmypaint-lang-1.3.0-1.3.noarch (@System)

Is it safe to proceed?

#5

OK - I solved my problem. I disabled the repo home:Herbster0815 and converted whatever was possible back to openSUSE. I had used this repo for a package (flvstreamer) which was not in the openSUSE or packman repo and over the time I must have switched packages to this repo. Now after zypper dup I had only 2 file conflicts - the same as kilbert at the beginning of this thread and another - something to do with painting software from the default install which I never used. After typing yes the install went ahead without problems and now after a reboot everything seems to be OK.

#6

Yes, that was your additional problem. I’m glad you have it solved.

#7

I experienced similar problems in the past. Now I am using priorities, which helps avoiding them. I also use zypper dup --allow-vendor-change --auto-agree-with-licenses. Only on very rare occasions zypper asks for manual action.

#  | Alias                            | Name                            | Enabled | GPG Check | Refresh | Priority | URI                                                                             
---+----------------------------------+---------------------------------+---------+-----------+---------+----------+---------------------------------------------------------------------------------
 2 | Packman                          | Packman                         | Yes     | (r ) Yes  | Yes     |   90     | http://ftp.fau.de/packman/suse/openSUSE_Tumbleweed/                             
 5 | download.opensuse.org-non-oss    | Haupt-Repository (NON-OSS)      | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/tumbleweed/repo/non-oss/                           
 6 | download.opensuse.org-oss        | Haupt-Repository (OSS)          | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/tumbleweed/repo/oss/                               
 7 | download.opensuse.org-tumbleweed | Hauptaktualisierungs-Repository | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/update/tumbleweed/                                 
 1 | Application_Geo                  | Application_Geo                 | Yes     | (r ) Yes  | Yes     |  100     | http://download.opensuse.org/repositories/Application:/Geo/openSUSE_Tumbleweed/ 
 3 | dl8fcl                           | dl8fcl                          | Yes     | (r ) Yes  | Yes     |  100     | https://download.opensuse.org/repositories/home:/dl8fcl/openSUSE_Tumbleweed/    
 8 | home_seife_testing               | testing (openSUSE_Factory)      | Yes     | (r ) Yes  | Yes     |  100     | http://download.opensuse.org/repositories/home:/seife:/testing/openSUSE_Factory/
 9 | http-opensuse-guide.org-37124e10 | libdvdcss repository            | Yes     | (r ) Yes  | Yes     |  100     | http://opensuse-guide.org/repo/openSUSE_Tumbleweed/                             
10 | jalbum                           | jalbum                          | Yes     | (  ) No   | Yes     |  100     | http://jalbum.net/download/software/yumrepo/                                    
11 | myrepo                           | myrepo                          | Yes     | ( p) Yes  | Yes     |  100     | dir:///home/karl/Downloads/myrepo                                               
erlangen:~ #

https://forums.opensuse.org/showthread.php/531333-Zypper-dup-priorities

#8

Yes, I use repo priorities and “–allow-vendor-change”. But I don’t force the “auto-agree”. This works out well.

Vendor changes are uncommon, at least recently.

#9

I thought the priorities don’t work any more? Further unless e.g. MM codec patents expire and are picked up by openSUSE I prefer not to allow vendor changes - and if there are any I would like to know that there were changes.

#10

They are still working here.

Further unless e.g. MM codec patents expire and are picked up by openSUSE I prefer not to allow vendor changes - and if there are any I would like to know that there were changes.

Fair enough.

I have tried both ways – with or without “–allow-vendor-change”. From my experience, I see the same updates either way. The only difference is that with “–allow-vendor-change”, I get a conflict dialog to approve them. I think these are all forced vendor changes, due to a package being removed from one of the repos (as happened after patent expiry).

If I do use “–allow-vendor-change”, the list of updates does include a list of vendor changes. But I haven’t seen any of those recently.

In my case, I only have the standard repos plus packman. And I have given the packman repo a better priority (smaller priority number).