Update Leap15 to 15.1 - what should be changed in future

I updated my 4th computer from Leap15 to 15.1 - it was the worst update I had in the approx 15 years using openSUSE (from version 9.2 onwards). On this computer I had the KDE framework and the KDE application repos since one of the programmes did not run with the package from the normal default repos. Over the time I had to switch more and more packages to these KDE repos to avoid conflicts and I never had problems with this computer (which is my wife’s computer - the most heavily used computer on the network). No during the upgrade with the software listing I had again this message of file conflicts and manual intervention required. I spend more time to allow a vendor change form those packages from the KDE repos and the packman repo to the openSUSE repo than the time required for the actual update - it must have been more than 1000 packages.
I think this is an unnecessary waste of time and the update would be greatly improved if the vendor change was already allowed in the upgrade with the normal (GUI) installer. Failing that there should be a setting to allow vendor change for the file conflicts. Secondly there should be an option to add more repos for the upgrade (e.g. packman) to avoid switching back to openSUSE and afterwards switching back to packman.

Sounds like you have mixed version repos. Show zypper lr -d (.Please use code tags (# in the tool bar)

Now after the update I have only the default repos from the install and packman.

As I described in another Forum thread,
I updated my personal 15.0 to 15.1 disabling the Packman repo, then choosing option 2 (Keep existing packages) instead of the default option 1 (change everything to the openSUSE 15.1 repo) for all the file conflict decisions. This ensured the least amount of re-installing and vendor changes.
After the system upgrade completed, then I re-enabled my Packman repo (but with the change to 15.1) and ran a system update (zypper up).
Everything so far is working fine.

I suspect you could have done the same thing with your KDE repos,
The reason for disabling “extra” repos besides the oss is to maximize the odds the system upgrade goes well.
Re-installing subcomponents by re-enabling the repo and installing packages from that repo separately ensures that if there are any undiscovered conflicts, your system should still boot and run.

I’d guess that the same procedure should work for your situation with your KDE repos.
Of course, you could also always take a massive chance that everything will perfectly if you leave your extra repos (KDE in your case) enabled during the upgrade.


I understand what you are saying, tsu2 but you still had to go manually through all the packages and tick the option 1 or 2. I had to go through more than 1000 options (in fact when I wanted to install calibre a few weeks ago the system wanted to change over 2000 packages so I installed the FBreader insead). I understand that to minimise the odds of failure there is the Install with the 4 main repos. So why not have the option “allow vendor change” and the tedious going though those options would be gone. I didn’t necessarily want to stay with those KDE repos - I wanted to have a working system and that is why I used those repos at the start to avoid one qt-package which had a minor bug which prevented firejail to work. The KDE repos had the newer version where everything worked. It just ended up that way with an endless list of options. That’s why I suggested that in future the install should have the option “allow vendor change”. If we could add addition repos (e.g. packman) it would be another advantage.

Yes, for me it wasn’t that bad, hitting “2” continuously for maybe 30 conflicts, but thousands would be impossible to deal with.

I’d recommend submitting a feature request to https://bugzilla.opensuse.org referencing this Forum thread, although a solution doesn’t immediately come to mind for me, I’d imagine someone can think of an efficient way to address this scenario in the future.