Tried to run a zypper dup on my new machine this morning showing up after retrieving 2223 packages in a TTY w/ screen -L . . . . ??? It said “file that conflict will be removed, possibly damaging your system, do you want to proceed?”
I aborted. Since I ran it in a TTY I couldn’t copy/paste the data . . . 1) file /usr/lib64/liblber.so.2.0.200 conflicts with file from package libldap2-2.6.8-1600000.1.16.x86_64
file /usr/lib64/libldap.so.2.0.200 conflicts with file from package libldap2-2.6.8-160000.1.16.x86_64
That is the general idea . . . . This was the second problem running a zypper on my Leap 16 installs. A few days back trying to dup on my older '12 Mac Pro edition of Leap 16 . . . hit a constant series of problem questions and issues with a large number of packages, that I also aborted out of that upgrade. That system wasn’t used for about a month, previously running fine.
That system isn’t mission critical as the one on my new machine, now waiting for 2223 package upgrade, in there two file conflicts interfering. OK to click “yes” and move forward with the zyppering?? Or, it is more technical than that?
With the latest zypper dup, libldap2-2.6.8gets removed from Leap 16 and replaced by libldap-2. But without any terminal output (even a picture would suffice), we can only guess what happened on your machine. Maybe the transaction order is different on your machine (installation before deinstallation). Or you performed a zypper up instead of dup.
Überprüfung auf Dateikonflikte läuft: ...............................................................................................................................................[Fehler]
2 Dateikonflikte festgestellt:
File /usr/lib64/liblber.so.2.0.200
from install of
libldap-2-2.6.10+10-160000.2.1.x86_64 (repo-oss (16.0))
conflicts with file from package
libldap2-2.6.8-160000.1.16.x86_64 (@System)
File /usr/lib64/libldap.so.2.0.200
from install of
libldap-2-2.6.10+10-160000.2.1.x86_64 (repo-oss (16.0))
conflicts with file from package
libldap2-2.6.8-160000.1.16.x86_64 (@System)
Dateikonflikte treten auf, wenn zwei Pakete versuchen, Dateien mit demselben Namen, jedoch anderen Inhalten zu installieren. Wenn Sie den Vorgang fortsetzen, werden die im Konflikt stehenden Dateien ersetzt, wobei der bisherige Inhalt verloren geht.
Fortfahren? [ja/nein] (nein):
But as @hui said and you can see in the info, that depends on the old/new package so I say yes to continue.
I said “yes” to allow the conflict. My reasoning was that it seemed to be a conflict between an older libldap and a newer one.
When the update completed, I did a check for orphaned packages, and that conflicting libldap showed up as orphaned. So I removed it, which presumably eliminated any possible problem.
@non_space you might want to run zypper se -is |grep "(System Packages)" to check (I found a few) and also the kernel version (It was a downgrade…) should be 6.12.0-160000.4-default
OK, thanks for the follow up . . . ran that command, but don’t know what it is telling me . . . ??? There was the “openh” stuff a bit back where I needed “mozilla-openhxxx” to get videos playing . . . without Packman. Haven’t yet tried to add Packman, as perhaps I don’t need it . . . but, what is “system packages” telling me in this instance?
Downgraded kernel seems to be in roper order . . . .
