neverending chain of file conflicts during zypper dup: digikam-libs

English Applications
1

Hello,
i am trying to do a zypper dup for weeks now but there are always new problems preventing me to do so, one of the problems that occured right in the beginning but was later superseded by others but after those were fixed is back again now, is the following


Checking for file conflicts: .................................................[error]
Detected 2 file conflicts:

File /usr/lib64/libkdcraw.so.23.0.0
  from install of
     digikam-libs-4.14.0-3.1.x86_64 (openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     libkdcraw23-15.08.3-1.2.x86_64 (@System)

File /usr/lib64/libkexiv2.so.11.3.0
  from install of
     digikam-libs-4.14.0-3.1.x86_64 (openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     libkexiv2-11-15.08.3-2.1.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): no

This is related to this thread here:
https://lists.opensuse.org/opensuse-factory/2016-01/msg00528.html
and to this request:
https://build.opensuse.org/request/show/356746

The number of file conflicts was larger in the beginning, but now as this is considered fixed there are still those two remaining. Is there a chance that this is getting solved in the near future, what would happen if i would continue with yes and replace the files?
I do not want to break anything but there are over 3000 upgrades in my list for weeks now which cannot be installed because of this.

2

What does


zypper up

do? AFAIK this is solved, some packages should be removed since they’re included in digikam-libs now, but when you dup you tell zypper to use these packages as upgrade candidates, hence raising the conflict. The packages simply cannot coexist.

3

zypper up shows the same conflicts.

4

I said “yes” on that conflict. This was on the principle that I should prefer newer software to older, particularly on a rolling release.

I then investigated. There were many orphaned packages. Once I had eliminated those, most of the problems disappeared. In particular, the older software with file conflicts appeared to be among the orphans. I described the orphan removal in more detail in a blog post.

I still see problems for a latex package. I should probably just delete that one package. And I still saw chromium conflicts. For chromium, I conceded defeat and install “chromium-ffmpegsumo” to replace “chromium-ffmpeg”. The chromium version in Tumbleweed repos and the “chromium-ffmpeg” version in packman have been out of sync for too long. If I see them back in sync, I’ll switch back to “chromium-ffmpeg”.

5

Ok thank you i just selected yes, also. Seems to work but i did not checked if digikam still works.