Upgrading your Chapeau 24 system to Fedora 27

As explained in the recent project announcement it is recommended to update your Chapeau system to Fedora 27.

This upgrade will turn your Chapeau installation into a Fedora installation but you will keep your applications and settings much like any other upgrade and you’ll ensure that your system is up to date and it remains supported going forward.

Before upgrading

Do ensure you have a system backup available or a disaster plan in case the upgrade fails.
Ensure you have at least 4GB of disk space available to /var before attempting the upgrade

  • If you are still running Chapeau 22 it is recommended to upgrade to Chapeau 23 first, if you’re particularly impatient a direct upgrade to 24 might just work but your mileage may vary.
  • If you are still running Chapeau 21 you will have to first follow the procedure ‘Upgrading to Chapeau 22‘.
  • If you are still running Chapeau 20 see the guides ‘Upgrading to Chapeau 21‘ and ‘Upgrading to Chapeau 22‘.
    Tip: You should be able to use fedup to skip 21 and upgrade to Chapeau 22, just ensure to include all post upgrade tasks detailed in both of the upgrade guides for 20 [link] & 21 [link] after the package upgrade. Then as fedup has been obsoleted past 21 it is recommended to then follow the guide for upgrading Chapeau 22 to Chapeau 23.

 

Upgrading your system

To upgrade your system perform the following tasks…

1. Open the Terminal application.

2. Update your system and reboot

Once rebooted login and reopen your terminal.

3. Begin the upgrade process.

Wait for DNF to download the packages to your system.

4. Reboot to continue the upgrade.

Once the previous command finishes downloading all of the upgrades, your system will be ready for rebooting into the upgrade process, type the following command in a terminal:

Your system will reboot into a non-interactive upgrade phase.
The upgrade phase can take a long time, sometimes a couple of hours and can appear at times to not be doing anything, be patient and leave it to complete.
Once the upgrade has finished successfully the system reboots and should start as it normally does.

5. Log in and reopen a terminal

Reinstall the RPMFusion repo packages

6. If you’ve installed Nvidia drivers…

It’s best to reinstall them after jumping to Fedora 27.

7. Update again and reboot

8. Update your Gnome Extensions

Visit extensions.gnome.org/local in Firefox.
Firefox may prompt you to allow the site to run “Gnome Shell Integration”, select [Allow] > [Allow and remember].

gnome_extensions_blocked

Installed extensions requiring an update are shown with a green icon, click each green icon to update them, once updated switch them on if required.

gnome_extensions_local

9. Optional post-upgrade tasks

After the upgrade finishes there are a few final steps you can do to clean up your system after the upgrade. These tasks can be ignored if no issues occurred during the upgrade and you do not require any new packages.

Most configuration files are stored in /etc. If there are any updates to them and you touched some of those files before, RPM creates new files with either .rpmnew suffix (the new default config file), or .rpmsave suffix (your old config file backed up). You can search for these files, go through the changes and make sure your custom changes are still included and the new defaults are applied as well. A tool that tried to simplify this is rpmconf. Install the package, and then use it as:

See more information in its manual page.

You can see list of packages with broken dependencies like this:

Ideally there should be none. If there are some, consider removing them, because they are not likely to work properly anyway.

You can see duplicated packages (packages with multiple versions installed) like this:

For ordinary packages, just the latest version should be installed. But there can be exceptions to the rule, only remove what you are sure you no longer need.

Some packages might stay on your system while they have been removed from the repositories. See them using:

If you don’t use these, you can consider removing them. Please note that this list is only valid if you have a fully updated system. Otherwise you’ll see all installed packages which are no longer in the repositories, because there is a newer update available. So before acting on these, make sure you have run sudo dnf update and generate the list of extra packages again. Also, this list might contain packages installed from third-party repositories for which an updated repository hasn’t been published yet. This often involves e.g. RPM Fusion or Dropbox.

You can remove no-longer-needed packages using:

but beware that dnf decides that a package is no longer needed if you haven’t explicitly asked to install it and nothing else requires it. That doesn’t mean that package is not useful or that you don’t use it. Only remove what you are certain you don’t need. If you use PackageKit (or GNOME Software, Apper, etc) for installation, this output might list even important apps and system packages, so beware.

Only follow up these steps if you have troubles with your upgraded system. It should not be needed in the vast majority of upgrades.

Rebuilding the RPM database

If you see warnings when working with RPM/DNF tools, your database might have gotten corrupted for some reason. It is possible to rebuild it and see if resolves your issues. Always back up /var/lib/rpm/ first. To rebuild the database, run:

 

Using distro-sync to resolve dependency issues

The system upgrade tool uses distro-sync method by default. If your system stayed partly unupgraded or you see some package dependency issues, you might try to fix it by running another distro-sync manually. This tries to make your installed packages exactly the same version as in currently enabled repositories, even if it meant downgrading some packages:

A stronger variant also allows to remove package for which package dependencies can’t be satisfied. Always carefully review which packages are going to be removed before confirming this:

 

Relabel files with latest SELinux policy

If you see warnings that some actions were not allowed because of current SELinux policy, it might be a case of having some files incorrectly label with SELinux permissions. This might happen in case of some bug or if you had SELinux disabled in some point of time in the past. You can relabel the whole system by running:

… and rebooting. The next boot will take a long time and will check and fix all SELinux labels on all your files.

 

Your Chapeau system has been upgraded to Fedora 27

Comments are closed.