You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following message appeared a while ago when trying to upgrade to 38.20230221.n.1 on my system, luckily I was able to skip it and upgrade to a posterior commit.
Checking out tree d6c9eee... done
Enabled rpm-md repositories: fedora-cisco-openh264 fedora-modular updates-modular updates fedora google-chrome code rpmfusion-free-updates-testing rpmfusion-free rpmfusion-nonfree-updates-testing rpmfusion-nonfree updates-archive
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2022-10-06T10:49:41Z solvables: 4
rpm-md repo 'fedora-modular' (cached); generated: 2023-02-20T09:16:19Z solvables: 1082
rpm-md repo 'updates-modular' (cached); generated: 2018-02-20T19:18:14Z solvables: 0
rpm-md repo 'updates' (cached); generated: 2018-02-20T19:18:14Z solvables: 0
rpm-md repo 'fedora' (cached); generated: 2023-02-20T09:23:27Z solvables: 68414
rpm-md repo 'google-chrome' (cached); generated: 2023-02-17T17:32:02Z solvables: 3
rpm-md repo 'code' (cached); generated: 2023-02-21T06:44:15Z solvables: 3077
rpm-md repo 'rpmfusion-free-updates-testing' (cached); generated: 2023-02-19T20:17:37Z solvables: 27
rpm-md repo 'rpmfusion-free' (cached); generated: 2023-02-19T20:30:14Z solvables: 477
rpm-md repo 'rpmfusion-nonfree-updates-testing' (cached); generated: 2023-02-19T20:50:58Z solvables: 2
rpm-md repo 'rpmfusion-nonfree' (cached); generated: 2023-02-19T20:57:16Z solvables: 223
rpm-md repo 'updates-archive' (cached); generated: 2022-11-11T05:17:33Z solvables: 0
Resolving dependencies... done
error: Could not depsolve transaction; 6 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
Problem 5: The operation would result in removing the following protected packages: systemd
Problem 6: The operation would result in removing the following protected packages: systemd
This seems to be a packaging bug on RPMFusion side, but rpm-ostree could at least tell me which packages are affected so I don't have to figure which packages one by one
Expected:
The error message should show which packages cause the depsolve to solve intead of only showing that it's a conflict with systemd and no info about how it conflicts.
Steps to reproduce it
Provide any additional data that may help debug this - which specific version of
an RPM is in the repo, or any host system configuration.
Install some RPMFusion packages on Fedora Silverblue 38 or install them on Fedora Silverblue 37 and try to rebase to 38.
Would you like to work on the issue?
No, I don't have any knowledge on how rpm-ostree works at the moment.
Notes: This error comes from libdnf. We'd have to enhance the code around here. Probably libdnf should use SOLVER_LOCK for protected packages like we do in #2125. That would cause libsolv itself to report a more helpful problem message. But probably not worth changing before moving to dnf5 and seeing if this bug reproduces.
Host system details
Expected vs actual behavior
The following message appeared a while ago when trying to upgrade to 38.20230221.n.1 on my system, luckily I was able to skip it and upgrade to a posterior commit.
This seems to be a packaging bug on RPMFusion side, but rpm-ostree could at least tell me which packages are affected so I don't have to figure which packages one by one
Expected:
The error message should show which packages cause the depsolve to solve intead of only showing that it's a conflict with systemd and no info about how it conflicts.
Steps to reproduce it
Provide any additional data that may help debug this - which specific version of
an RPM is in the repo, or any host system configuration.
Install some RPMFusion packages on Fedora Silverblue 38 or install them on Fedora Silverblue 37 and try to rebase to 38.
Would you like to work on the issue?
No, I don't have any knowledge on how rpm-ostree works at the moment.
The related bug on Silverblue tracker is fedora-silverblue/issue-tracker#422
The text was updated successfully, but these errors were encountered: