View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001750 | Rocky-Linux-9 | [Repo] Extras | public | 2023-01-05 13:32 | 2023-01-05 17:48 |
| Reporter | Andrew Bauer | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0001750: Package conflict between rpmfusion-free-release found in Rocky Extras and RPMFusion | ||||
| Description | NOTE: As far as I can tell, the following change came from Rocky Linux, rather than an upstream source. Please advise if this is not the case. Beginning with Rocky Linux 9, rpmfusion-free-release was built with the %{dist} tag in Release. https://dl.rockylinux.org/pub/rocky/9/extras/source/tree/Packages/r/rpmfusion-free-release-9-1.el9.src.rpm Note, however, this is a change from Rocky Linux 8, which does not include the release tag. https://dl.rockylinux.org/pub/rocky/8/extras/source/tree/Packages/r/rpmfusion-free-release-8-0.1.src.rpm Note that the RPMFusion team does NOT include the %{dist} tag in their package: https://github.com/rpmfusion/rpmfusion-free-release/blob/el9/rpmfusion-free-release.spec#L6 This has caused the following package conflict, when attempting to use the subpackage(s) currently hosted only at RPMFusion and not Rocky Linux: >$ sudo dnf update >Last metadata expiration check: 0:11:34 ago on Sat Dec 31 08:09:12 2022. >Error: > Problem: package rpmfusion-free-release-tainted-9-1.noarch requires rpmfusion-free-release = 9-1, but none of the providers can be installed > - cannot install both rpmfusion-free-release-9-1.el9.noarch and rpmfusion-free-release-9-1.noarch > - cannot install both rpmfusion-free-release-9-1.noarch and rpmfusion-free-release-9-1.el9.noarch > - cannot install the best update candidate for package rpmfusion-free-release-tainted-9-1.noarch > - cannot install the best update candidate for package rpmfusion-free-release-9-1.noarch >(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) To avoid this issue both now and in the future, I would suggest building the rpmfusion-free package without making any changes to the upstream specfile, no matter how trivial. Would the Rocky team also include all subpackages (tainted and next) found within said specfile. Thank you. | ||||
| Steps To Reproduce | 1) dnf install rpmfusion-free-release (from Rocky Extras repo) 2) dnf install rpmfusion-free-release-tainted (from the RPMFusion repo) 3) dnf update | ||||
| Additional Information | In case you were wondering why RPMFusion does not build rpmfusion-free-release with the %{dist} macro in Release, I asked the same question and was told they are unwilling to change. See: https://bugzilla.rpmfusion.org/show_bug.cgi?id=6545 | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-01-05 13:32 | Andrew Bauer | New Issue |
