Just one little bit about 0.7.2:
since this release masquerading is off by default for IPv6. To get back to the old behaviour you have to manually insert one rich rule in the external zone:
firewall-cmd --permanent --zone=external --add-rich-rule="rule family=ipv6 masquerade"
…that actually cost me about one day to realize that this was the root cause of my network troubles after upgrading my firewall from 15.0 to 15.1…
I just got updated to Thunderbird 68.0 on my linux desktop systems.
Started it, and found that ALL add-ons except two had been disabled or removed, and the two that were left did not do anything anymore.
For example, lightning was still there but there was no way to actually open your calendar.
Good thing I had a way to roll back to 60.8. That one works the way I need it to.
I put together a second page with tips for firewalld…
So I’ve used my trusted little leapup script for an upgrade from 42.3 to 15.0, and in three out of three cases it was not fun…
On my two cloud servers all I had was some glitchiness with the firewall, and I have to figure out how to rebuilt the latest version ot the xtables addons on Leap 15.
On my desktop I guess I’ve screwed up during the first stage of the upgrade, and missed one dependency quirk or someting, but … that left me dead in the water on that machine. Actually had to do a standard upgrade from DVD on that one.
I am not looking forward to upgrading the main firewall. Guess that’ll wait until my laptop comes back from repairs so I can use that one as a second testbed.
That being said, I found a few typos in my leapup script that bit me in the *** too.
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.
Update: There is now a RPM package for openSUSE Leap 42.3 and 15.0 here: https://software.opensuse.org/package/leapup?search_term=leapup
this time I went directly from 13.2 to Leap 42.2, skipping the intermediate step of Leap 42.1…. and no problems. I like that.
For your convenience here is the link to how I do this.
Oops I Did It Again…
Live Upgrade, with my tried and trusted method. By now that method is so polished that I had no issue whatsoever, so I did all three computers at the same time. I’m just glad to have a decent internet connection… I think the total downloads added up to somewhere near 15 gigabyte.
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.
I just finished a major heart surgery on my laptop. Many thanks to the guys who made some youtube tutorials about taking that laptop apart! The Acer E5-571G is definitely NOT built to be taken (apart) lightly (Here is the german tutorial that I was following, and here is an english one).
After swapping out the 2x 4G memory modules for 2x 8G ones, and the 1TB laptop hard disk drive for a 1TB SSD disk, and putting everything back together, the real fun began:
- install the old harddisk in an external USB3.0 harddisk enclosure (the drive was still good after all)
- boot from a Windows 10 installer
- partition the disk and install Windows 10 in about half of the available space
- the usual windows installation hijinx: install a driver, reboot, repeat ad nauseam
- when windows is about done with the initial installation stuff, plug in the old harddisk on USB3.0 and copy the data from your old user account to your new
Then the linux fun begins, but be aware that this method will only work if the existing linux installation on the old disk was based on a LVM setup!
That’s it folks!
I finally updated my last machine from openSUSE 12.3 to 13.1 (in the usual way), and with that one I had a bit more fun than the other few times I’ve done this by now.
First mysql refused to start, then quite a few services that were enabled on 12.3 decided to be disabled on 13.1, but nothing during the update “told me so”… but now all seems to work fine.