After switch from Tumbleweed to OpenSuse 15.4 Beta I see conflicts with packages from same repository, how to fix ?
> zypper in -f procps
Loading repository data…
Reading installed packages…
Forcing installation of ‘procps-3.3.15-7.22.1.x86_64’ from repository ‘Main Repository’.
Resolving package dependencies…
The following package is going to be reinstalled:
procps
1 package to reinstall.
Overall download size: 257.7 KiB. Already cached: 0 B. No additional space will be used or freed after the operation.
**Continue? [y/n/v/…? shows all options] (y): **y
Retrieving package procps-3.3.15-7.22.1.x86_64 (1/1), 257.7 KiB (639.6 KiB unpacked)
Retrieving: procps-3.3.15-7.22.1.x86_64.rpm …[done (1.2 KiB/s)]
Checking for file conflicts: …[error]
Detected 4 file conflicts:
File /bin/pgrep
from install of
procps-3.3.15-7.22.1.x86_64 (Main Repository)
conflicts with file
/usr/bin/pgrep
from install of
procps-3.3.15-7.22.1.x86_64 (Main Repository)
File /bin/pkill
from install of
procps-3.3.15-7.22.1.x86_64 (Main Repository)
conflicts with file
/usr/bin/pkill
from install of
procps-3.3.15-7.22.1.x86_64 (Main Repository)
File /bin/ps
from install of
procps-3.3.15-7.22.1.x86_64 (Main Repository)
conflicts with file
/usr/bin/ps
from install of
procps-3.3.15-7.22.1.x86_64 (Main Repository)
File /sbin/sysctl
from install of
procps-3.3.15-7.22.1.x86_64 (Main Repository)
conflicts with file
/usr/sbin/sysctl
from install of
procps-3.3.15-7.22.1.x86_64 (Main Repository)
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): **
Filesystem layout in Tumbleweed is incompatible with current Leap. It works updating one way - from Leap to Tumbleweed - but nobody implemented switch in backward direction. You better do new clean install.
You do not tell how you did that “switch”, but the fact that you mention Tumbleweed suggests that you did different then a fresh installation to achieve that switch. I know of no supported way to do this except by a fresh installation (which then would remove every remembrance of Tumbleweed when done over the same disk space.).
The question is NOT what roughly your path is, but what you exactly did. Did you a fresh installation, or did you use some Upgrade feature (from the ISO image, or by changing repos and doing zypper dup, or whatever).
A fresh installation is using the installer ISO and then doing an installation and telling it to re-use (often called re-format) the partition where the root file system is on, by the new root file system. Thus erasing everything from the old installation (except of course user data you may have on another file system, or may have saved elsewhere).
Apart from us trying to understand what you exactly did, it may be usefull to show what repos you have now:
As already said above, that is not supported. In fact only minor steps like very soon from 15.3 > 15.4 are tested and supported for this feature. Not switching from Leap to Tumbleweed and back.
Also, as @avidjaat hinted at. when you use Btrfs as file system type, backward compatibility between TW and Leap is not guaranteed.
You could try to repair by first disabling all the extra repos (including Packman), then do a
zypper dup.
Then see if your problem is gone.
After that enable Packman and do the Vendor switch to it.
Then enable the other repos you seem to need, install from them what you need and my suggestion is then to disable them until you think there is an update there that you need.