Rpm-ostree update fails since trying to remove protected packages : systemd

Ask Fedora
, , ,
1

seems like somthing is Fudget now ostree uopdates are failing since something wants to reemove systed packages from system

⠓ Receiving objects; 93% (1073/1146) 11.5 MB/s 207.2 MB                                                       436 metadata, 754 content objects fetched; 204650 KiB transferred in 20 seconds; 333.2 MB content written
Receiving objects; 93% (1073/1146) 11.5 MB/s 207.2 MB... done
Checking out tree d06dec1... done
Enabled rpm-md repositories: fedora-cisco-openh264 updates fedora copr:copr.fedorainfracloud.org:phracek:PyCharm google-chrome rpmfusion-nonfree-nvidia-driver rpmfusion-nonfree-steam nordvpn updates-archive
Updating metadata for 'updates'... done
Updating metadata for 'updates-archive'... done
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2024-03-11T19:22:31Z solvables: 3
rpm-md repo 'updates'; generated: 2024-11-15T01:16:20Z solvables: 9019
rpm-md repo 'fedora' (cached); generated: 2024-10-25T08:41:19Z solvables: 76624
rpm-md repo 'copr:copr.fedorainfracloud.org:phracek:PyCharm' (cached); generated: 2024-08-12T11:59:47Z solvables: 5
rpm-md repo 'google-chrome' (cached); generated: 2024-11-15T08:40:04Z solvables: 4
rpm-md repo 'rpmfusion-nonfree-nvidia-driver' (cached); generated: 2024-11-04T07:30:59Z solvables: 17
rpm-md repo 'rpmfusion-nonfree-steam' (cached); generated: 2024-10-03T14:20:29Z solvables: 2
rpm-md repo 'nordvpn' (cached); generated: 2024-09-30T13:59:42Z solvables: 32
rpm-md repo 'updates-archive'; generated: 2024-11-15T01:29:39Z solvables: 8286
Resolving dependencies... done
error: Could not depsolve transaction; 4 problems detected:
 Problem 1: The operation would result in removing the following protected packages: systemd
 Problem 2: The operation would result in removing the following protected packages: systemd
 Problem 3: The operation would result in removing the following protected packages: systemd
 Problem 4: The operation would result in removing the following protected packages: systemd
2

Possibly one of the layered packages causing it.

Do you have any packages layered from outside of the current repos?

3

all layers i have only Nvidia and VPN

Deployments:
● fedora:fedora/41/x86_64/kinoite
                  Version: 41.20241116.0 (2024-11-16T00:54:31Z)
               BaseCommit: d06dec159161551845ed653a56cc5120779344dc45d310046886e6c51adb343f
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
          LayeredPackages: akmod-nvidia akmods nordvpn-3.18.5 rpmdevtools xorg-x11-drv-nvidia-cuda
            LocalPackages: akmods-keys-0.0.2-8.fc41.noarch
4

I know rpm-fusion packages only need to be uninstalled and layered again between major releases, so it shouldn’t be an issue here.

If you’re willing to do the effort, you could try temporarily unlayering[1] nordvpn, to see if it is causing it.

  1. Is this a word? ↩︎

5

why nordvpn wants to remove systemd it is using it and if there is systemd installed only for nordvpn it still wouldnt install or upgrade nordvpn since i am forced it to use 3.18.5 version only since that is latest working and stable version new ones wont work on atomics at all

6

It was just a guess, since nordvpn is pulled from a repo in sync with centOS and not with F41 afaik.

Either way, I expect such errors to be caused by specific layered packages, so I guess one of them could be the culprit.

7

Added packages, rpm

8

Is that so?

I also got strange issues trying to rebase from 40 → 41

This is a bit annoying

9

Never removed any layers on upgrade or rebase before

40 to 41 is issue and best way is to fresh install due dnf 4 change to dnf5 you end up bricked system if upgrade

10

According to the FAQ from this Fedora Magazine article, if there are RPM Fusion repo packages layered, they should be removed and readded before rebasing.

11

Normally no need to do that, but I can see dependency issues possibly occurring with packages from external repos. The original error indicates issues in resolving dependencies, and I expect depsolve checks to be done against layered packages, but not against packages within the ostree image.

I don’t think dnf could be the issue, given that it is not available in the ostree deployment, but only in container images.

12

My suspicion is that the package akmods from RPM Fusion is causing this error, since it depends on systemd.

I arrived to this conclusion today, when I tried to install Silverblue 40 on an old machine (MacBook). Since this machine has a Broadcom wireless chip requiring a proprietary driver, I tried layering the broadcom-wl package. This package requires akmod-wl, which requires akmods, which in turn depends on systemd.

The Nvidia drivers from RPM Fusion require the same akmods package to build the specific kernel modules IIRC, hence the same behavior and probably the same root cause.

I have filed a bug on RPM Fusion’s issue tracker. You might want to add a comment if you consider the two issues are related.

1 Like
13

Initial investigation in Package broadcom-wl (via akmods) from RPM Fusion conflicts with systemd (#56) · Issues · fedora / Fedora Atomic Desktops / SIG Issue Tracker · GitLab.

1 Like