Aug 022017

Hi everyone,


I’ve started to put my trusted approach to seamless openSUSE upgrades into an easy to use shell script.

The script operates under a few assumptions (yes I know, assume makes an ass out of you and me), but what can you do, except calling them prerequisites:

  • Your system has all the latest updates applied according to your current repository setup (run “zypper patch; zypper dup” until there is nothing left to install)
  • All enabled repositories have priorities set that make it crystal clear which of them are preferred over which in case a package appears in more than one repo
  • All enabled repositories also exist for the target version, and use a repository URL that has that version number in it, and where the version number is the only difference between versions (this should usually be true for repositories from OBS and/or packman, buy YMMV)

If all this is true, running the script will create a backup of your current repository structure under /etc/zypp/repos.d_(current_version), and a repo setup for the target version under /etc/zypp/repos.d_(target_version), and then link the new structure to /etc/zypp/repos.d, and after that it will clean zyppers cache, refresh all repositories, and tell you the commands to execute to actually run the upgrade.

You might want to do those commands inside a screen session. You have been warned.

This script is provided with no warranty at all. Use it at your own risk. If you break things you get to keep the pieces.

If by any chance your root filesystem is on either LVM or btrfs, do a snapshot before you start upgrading your system.

Download the script here: leapup.tar.xz

So far I have used this script on two desktop systems which each use 20++ different repositories from OBS and packman, and no problems (aside from a few glitches in 42.3 that are connected to the nvidia drivers, but not to this upgrade process).


Update: in the last 4 days I updated five different machines using my script: my desktop computer which runs with 23 different repositories from OBS, my laptop and my work laptop which both run with 25 repos, my cloud host which runs with 10 repositories and my internal server/firewall which also runs with 10 repositories… no problems so far.

 Posted by at 11:57
Sep 142016

I upgraded my laptop to Leap 42.1 the other day, using the good old method that I’ve been talking about a few times. Worked without major issues, I just had to manually fix the repository URL in a couple of the repositories I’m using.

Now I’m on 42.1 using Plasma 5, and so far I mostly like it. A few features and settings have gone from parts of the kdepim suite, and there is one weird glitch-error where starting kopete gets me a weird “file: ioslave has been terminated” error, that I’m sure is somehow related to kopete styles. Maybe when I’ll do my desktop I’ll do the upgrade to Leap first, and then the upgrade to the latest plasma5, and not the other way around like on this laptop.

On the whole I’m happy with what I have here.

One little thought just keeps nagging me:

How come that Plasma 5 with the breeze style looks a LOT like Windows 10? …, wait, Windows 10 came after Plasma 5, right?

Edit, 2016-09-14: Turns out I should have done the upgrade to Leap 42.1 first, and THEN the KF5 update. I had some repositories enabled that should not be mixed. Disabled the bad ones, zypper dup -l, all is well.

 Posted by at 08:29
Oct 122012

I hate it when a mandatory update takes away functionality. In this case: twitter tools for WordPress.

The latest update now uses the “Social” plugin which integrates your blog with not only Twitter but Facebook as well. But it also takes away the option to have specific hashtags in your tweets about new blog posts.

Optimization WordPress Plugins & Solutions by W3 EDGE
%d bloggers like this: