Dnf mark issues in F39 to F40 upgrade

I used dnf system-upgrade to upgrade from F39 to F40, and there are some record issues (I don’t really know how to call them…):

  1. “ghostscript-tools-fonts”, “ghostscript-tools-printing” are now marked as user installed, but they should really be dependencies to “ghostscript” etc.
    This is easy to solve sudo dnf mark remove ghostscript-tools-fonts ghostscript-tools-printing.
    However why does this happen?

  2. “Desktop Accessibility” is listed as explicitly installed in dnf group list installed unlike other groups that belong to “Fedora Workstation” environment group.
    sudo dnf group remove "Desktop Accessibility" makes dnf think it’s really not installed, as it doesn’t show up in sudo dnf group upgrade "Fedora Workstation".[1]
    And, orca is still kept and considered group installed for whatever reason.

$ dnf repoquery --installed --qf='%{name}-%{evr}.%{arch} (%{reason})' orca-46.1-1.fc40.noarch
orca-46.1-1.fc40.noarch (group)
$ dnf repoquery --groupmember orca-46.1-1.fc40.noarch
orca-46.1-1.fc40.noarch
  @desktop-accessibility
  1. “snapshot” was made part of “gnome-desktop” group instead of “cheese”, I installed snapshot before the change, and it’s still marked user installed.
    This is easy to solve and is my fault. sudo dnf mark group snapshot-46.2-1.fc40.x86_64 [2].

  2. F40 removes X11, but “base-x” optional group is still installed.
    This is easy sudo dnf group remove base-x.

I suppose this is an XY problem. I just wish that system-upgrade equals to fresh install with Everything installer selecting “Fedora Workstation” group (as I initially installed the system this way[3]), without having to play nannies to fix up problems.


  1. Remove the explicit dnf mark on “Container Management” (No solution) ↩︎

  2. Dnf mark group doesn’t make package part of a group (this statement is false however) ↩︎

  3. Workstation Live image marks some packages as group without having a group installed ↩︎

Added dnf, dnf-system-upgrade and removed gnome

Added f40

Added dnf-system-upgrade

F* me, the Server edition is even worse. Most of these here aren’t supposed to be user installed but group installed or dependency.

$ dnf repoquery --userinstalled
appstream-0:1.0.2-2.fc40.aarch64
appstream-data-0:40-6.fc40.noarch
audit-rules-0:4.0.1-1.fc40.aarch64
authselect-0:1.5.0-5.fc40.aarch64
avahi-0:0.8-26.fc40.aarch64
caddy-0:2.7.6-2.fc40.aarch64
ddclient-0:3.11.2-3.fc40.noarch
efibootmgr-0:18-6.fc40.aarch64
fedora-logos-httpd-0:38.1.0-5.fc40.noarch
gdbm-1:1.23-6.fc40.aarch64
gnutls-dane-0:3.8.5-1.fc40.aarch64
julietaula-montserrat-fonts-1:7.222-7.fc40.noarch
kernel-0:6.8.4-200.fc39.aarch64
kernel-0:6.8.7-200.fc39.aarch64
kernel-0:6.8.7-300.fc40.aarch64
kernel-core-0:6.7.9-200.fc39.aarch64
kernel-core-0:6.8.4-200.fc39.aarch64
kernel-core-0:6.8.7-200.fc39.aarch64
kernel-core-0:6.8.7-300.fc40.aarch64
kernel-modules-0:6.8.4-200.fc39.aarch64
kernel-modules-0:6.8.7-200.fc39.aarch64
kernel-modules-0:6.8.7-300.fc40.aarch64
kernel-modules-core-0:6.8.4-200.fc39.aarch64
kernel-modules-core-0:6.8.7-200.fc39.aarch64
kernel-modules-core-0:6.8.7-300.fc40.aarch64
langpacks-en-0:4.0-12.fc40.noarch
libevdev-0:1.13.1-4.fc40.aarch64
libsoup3-0:3.4.4-3.fc40.aarch64
libtool-ltdl-0:2.4.7-10.fc40.aarch64
lvm2-0:2.03.23-1.fc40.aarch64
passim-0:0.1.5-3.fc40.aarch64
passim-libs-0:0.1.5-3.fc40.aarch64
pkcs11-provider-0:0.3-2.fc40.aarch64
podman-5:5.0.1-1.fc40.aarch64
python3-boto3-0:1.34.78-1.fc40.noarch
python3-botocore-0:1.34.78-1.fc40.noarch
python3-jmespath-0:1.0.1-6.fc40.noarch
python3-s3transfer-0:0.10.1-1.fc40.noarch
rpm-plugin-audit-0:4.19.1.1-1.fc40.aarch64
sdubby-0:1.0-8.fc40.noarch
setools-console-0:4.4.4-2.fc40.aarch64
systemd-boot-unsigned-0:255.4-1.fc40.aarch64
unbound-0:1.19.3-1.fc40.aarch64
wget2-0:2.1.0-8.fc40.aarch64
wget2-libs-0:2.1.0-8.fc40.aarch64
wget2-wget-0:2.1.0-8.fc40.aarch64
xfsprogs-0:6.5.0-3.fc40.aarch64
zlib-ng-compat-0:2.1.6-2.fc40.aarch64

I guess reinstalling Fedora every few versions is unavoidable if anyone has OCD about the tidiness/correctness of the packages.

To be honest, I get around this problem by removing all groups and using a list of carefully selected packages.

This also solves some issues when upgrading the system to the next release, such as the installation of unwanted packages.

1 Like