Checking upgrade paths

To check an upgrade path works:

find a test Fedora system,
make sure none of the new packages are already installed^[1],
install part or all of the old package set,
copy the new packages to a local directory^[2],
run createrepo on this directory^[3],
point dnf to it^[4],
try a dnf upgrade.
if that fails, try to understand why, rpm -e whatever dnf upgrade installed and repeat from step 1.

You can also use:

rpm -qp --obsoletes mypackage

… to check the obsoletes declared by one of your new packages and,

dnf list obsoletes

before the dnf upgrate to check what dnf thinks about your new packages^[5].

Notes:

↑ It would confuse the tools.
↑
If you're creating them:
1. adapt the previous spec file or create a new one,
2. mock/koji-build the result.
↑
```
createrepo <directory>
```

↑ Use a repo file such as this one:

[tmp]
name=tmp
baseurl=file:///tmp/rpm
enabled=1
gpgcheck=0

↑ But that won't check scriptlets and other packaging bits so do check dnf upgrade works afterwards.

Fonts in Fedora
The Fonts SIG takes loving care of Fedora fonts. Please join this special interest group if you are interested in creating, improving, packaging, or just suggesting a font. Any help will be appreciated.