It messed with DNS resolution for my local network, at least temporarily. I couldn’t resolve any websites that needed to hit our local DNS server. I did some Googling and saw that the resolver tech was changed from Fedora 32 to Fedora 33. I change a setting for my NIC and then changed it back and either that fixed it or (some websites mentioned just needing to give it some time). Either way, that was it. Relatively smooth.

While new versions of Fedora have been pretty darned stable for a few years now, I usually wait a while after a release to upgrade. This year waiting ended up turning into just leaving it alone. But with February half-way done, we’re actually starting to get kind of close to the Fedora 34 release date. So I figured President’s Day was as good a day as any to do the upgrade.

It came out this Tuesday and last night I updated my laptop. The only thing I had to do for the upgrade was remove a python3-test package. Since I’m using virtual environments, for the most part I don’t care which Python packages the system has. So that was a nice, easy upgrade! Good job Fedora packagers and testers! Speaking of Python, it’ll be nice to start upgrading my projects to Python 3.9. (Fedora 33 includes the latest programming language versions as part of its “First” values)

It’s been about a month since Fedora 32 was released, so I decided to try and upgrade Supermario to Fedora 32. First I had to disable the dropbox repo since they don’t have a Fedora 32 binary yet. Other conflicts included:

• bat in module
• gimp in module
• meson in module
• ninja in module
• pythnon3-pytest-testmon (doesn’t belong in a distupgrade repo)
• python2-beautifulsoup neds python2-lxml

The python ones are no-brainer to me. I use virtual environments now so I don’t care about the system libraries. I can get rid of those.

Because I have this VM registered to Katello (Foreman plugin) to receive updates (basically as a way of both keeping track of the computers and VMs on my network and also to have a GUI to pulp for caching RPMs), I had to deal with Katello-Agent. The latest RPM in the official Foreman/Katello repos is unfortunately for Fedora 29. That version of Fedora has been out of maintenance for a long time. Maybe Foreman (upstream for Satellite) is just used by most of their customers for RHEL sites that don’t have any Fedora nodes? So I did find this copr that provides updated versions: https://copr.fedorainfracloud.org/coprs/slaanesh/system-management/

Recently upgraded my server to Fedora 31 as the Fedora 30 support window had closed. All I had to do was disable the bat Modular Repo. It wasn’t obvious I needed to do this at first, but I found a bugzilla that covered it. Then everything proceeded.

I also updated my main laptop to Fedora 32; it’s always my first upgrade since it’s not my main machine. That one required a few modular repos to be disabled as well as a bunch of conflicts from Python 2 packages. By using dnf’s –auto-erase (or whatever the command actually is), everything proceeded and seems to be running just fine. I was a little worried at first with the warning about coming back from a locked screen in KDE, but I decided I could live with it on the laptop. So far, either the issue doesn’t affect my laptop or I haven’t triggered the conditions.

Back when Fedora 30 came out, I updated my laptop, but I left my main computer and the HTPC on Fedora 29. The former because I was busy with something at the time and didn’t want the disruption of an upgrade; the latter because the family depends on it for entertainment. However, with Fedora 31 coming out next Tuesday, the support window of Fedora 29 is over. The HTPC didn’t give any issues when I started the upgrade (at of this time it’s still running the upgrade), but my main computer did. This time it complaint about ripright and whois-mkpasswd.

I was able to get Kurio, my netbook, to upgrade to Fedora 23 without issue. BlueYoshi, the living computer, is still unable to upgrade. So far it’s tripping up on dolphin-emu, OBS-MP, and some Gnome package. I’m not sure if that’s something that’ll be fixed as RPMFusion continues to update their Fedora 23 packages or if I’ll have to do the old uninstall/reinstall dance that I sometimes have to do with these non-free packages that don’t get QA’d for a Fedora release. Not going to be doing my main computer any time soon.

Tried to upgrade the living room computer to Fedora 23. As of the time when I tried, because the RPMFusion repo wasn’t ready for Fedora 23, it couldn’t upgrade. I’ll try again in a day or two if the repo is up.

As many of you know, according to the Google search terms that bring people here.  I am of the not-so-humble opinion that Fedora’s upgrade process is about as pleasant as being forced to walk through the desert without a canteen of water.  First of all, they recommend to just do a fresh install which is a non-starter for me.  I’d have to waste way too much time restoring all my files and settings.  Ubuntu and Debian seem to get me through upgrades without reinstalling without any problems.  I blogged about the horrors up upgrading to Fedora 8 here and here.  I blogged about how awesome the yum upgrade worked here, here, here, and here.