Open MateusRodCosta opened 1 year ago
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 https://github.com/coreos/rpm-ostree/pull/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 https://github.com/fedora-silverblue/issue-tracker/issues/422