zeldor.biz

Linux, programming and more

Copyright © 2025
Log in

Upgrade opensuse 42.1 to 42.2

November 5, 2016 by Igor Drobot 4 Comments

countdown-leap-42-2-alex

openSUSE 42.2 Leap is still at the moment in RC2 state but a upgrade is already possible.

More information about 42.2 Leap can be found in the official release notes

I have a fresh installed 42.1 which is fresh patched so the first step will be the replacing of repository information:

1
2
cd /etc/zypp/repos.d
sed -i 's/42.1/42.2/' *

cd /etc/zypp/repos.d sed -i 's/42.1/42.2/' *

Load new repositories:

1
zypper refresh

zypper refresh

Now you can start the upgrade procedure:

1
zypper dup

zypper dup

The final step is a reboot:

1
init 6

init 6

Filed Under: Linux Tagged With: 42.2 Leap, openSUSE

Categories

Archives

Tags

apache2 Apple arduino ARM Automation backup bash Cisco Cluster Corosync Database Debian Debian squeeze DIY DNS Fedora FTP Fun Icinga Ipv6 KVM Linux LVM MAC OS X Monitoring MySQL Nagios Nginx openSUSE OpenVPN PHP Proxy Python python3 qemu RAID rsync Samba security ssh Ubuntu virtualization Windows Windows 7 Wordpress

Comments

  1. Roshan Hiripitiyage says

    May 5, 2020 at 19:25

    Hi Zeldor,

    Thanks.I was able to get the updates by following your guide lines.

    Thanks
    Roshan

  2. zeldor says

    December 11, 2016 at 23:55

    Razvan, thank you. Downloading first all packages is indeed helpful, OpenSUSE repositories are often not reachable or packages are not available(404).

  3. Razvan Mihaiu says

    December 11, 2016 at 22:09

    This worked great for me. Once change though:

    sudo zypper dup –download-in-advance

    It’s always better to download all the files in advance. I mean, I don’t even understand why this is not the only way to perform an upgrade (or at least, it should be the default one).

    The official upgrade file provided by OpenSuse is so damn intimidating. Without your small article I would have given up on this for now.

  4. THN says

    November 16, 2016 at 12:43

    Well, this looks like a blind flight. It might work in a close-to-ideal setup, but you’re ignoring all possible interdependencies with third party PPAs which people may have in their 42.1 repo list today. It would be more safe to remove those before doing the upgrade and then add them back in afterwards.

Leave a Reply

Your email address will not be published. Required fields are marked *

Yeaaah Cookie! We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.Ok