Update was easy, 15.2, I see you!

dyfet · July 9, 2020, 6:46pm

I had a real nice update experience. I did the in-place network cli method, changing all the zypp repos to use $releasever, including the obs ones, and then used the

zypper --releasever=15.2 refresh

policy override to do my migration and then zypper dup. I had a mix of obs repos, and over 6000 packages on my dev laptop too. The biggest issues were a few packages that wanted to do vendor migration, and I got rid of a few repos I no longer felt I needed right before the migration to make it a little simpler.

This makes me feel much more comfortable with deploying and maintaining dedicated opensuse or suse servers and devices in future products, which would have far less repo complexity and far less packages. Containers do full system snapshots, so those have less issues, and I could see building docker images from tumbleweed for that.

nrickert · July 9, 2020, 7:24pm

I’m glad it worked well. And that method did work well here in my tests.

You could have used:


zypper --releasever=15.2 dup --allow-vendor-change

to avoid being prompted for vendor changes.

dyfet · July 9, 2020, 9:53pm

nrickert:

I’m glad it worked well. And that method did work well here in my tests.

You could have used:
zypper --releasever=15.2 dup --allow-vendor-change
to avoid being prompted for vendor changes.

I actually didnt want some of the vendor changes, it wanted to change packman back to opensuse for some multimedia libs…but that seems handy.

dyfet · July 9, 2020, 10:43pm

nrickert:

I’m glad it worked well. And that method did work well here in my tests.

You could have used:
zypper --releasever=15.2 dup --allow-vendor-change
to avoid being prompted for vendor changes.

I actually didnt want some of the vendor changes, but it also wanted to change packman back to opensuse for some multimedia libs…but that seems handy.