Bug 1911825
| Summary: | cockpit-dashboard package does not get removed on upgrade | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Martin Pitt <mpitt> |
| Component: | cockpit | Assignee: | Matej Marušák <mmarusak> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 33 | CC: | alexandermurashkin, cstratak, dperpeet, extras-qa, mhroncok, mmarusak, mpitt, pvolpe, stefw |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | cockpit-237-1.fc33 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1911766 | Environment: | |
| Last Closed: | 2021-02-11 01:43:05 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1911766 | ||
| Bug Blocks: | |||
|
Description
Martin Pitt
2020-12-31 15:28:50 UTC
Matej, is that something you can look into, please? Apparently "Obsoletes" is not strong enough, maybe it needs "Conflicts:" or whatnot? The new package needs to also provide the name of the old for a clean upgrade path. See also: https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages That conflict is present as well at my machine. "If a package supersedes/replaces an existing package without being a sufficiently compatible replacement as defined above, use only the Obsoletes: line from the above example." We want to go this way. The current spec is broken though, see https://github.com/cockpit-project/cockpit/pull/15244 > That conflict is present as well at my machine. What conflict is that? (In reply to Matej Marušák from comment #3) > "If a package supersedes/replaces an existing package without being a > sufficiently compatible replacement as defined above, use only the > Obsoletes: line from the above example." > We want to go this way. The current spec is broken though, see > https://github.com/cockpit-project/cockpit/pull/15244 > > > That conflict is present as well at my machine. > > What conflict is that? When doing a dnf update: Problem 1: package cockpit-bridge-235-1.fc32.x86_64 conflicts with cockpit-dashboard < 233 provided by cockpit-dashboard-232-1.fc32.noarch - cannot install the best update candidate for package cockpit-bridge-232-1.fc32.x86_64 - problem with installed package cockpit-dashboard-232-1.fc32.noarch Problem 2: package cockpit-system-235-1.fc32.noarch requires cockpit-bridge >= 235-1.fc32, but none of the providers can be installed - package cockpit-bridge-235-1.fc32.x86_64 conflicts with cockpit-dashboard < 233 provided by cockpit-dashboard-232-1.fc32.noarch - cannot install the best update candidate for package cockpit-system-232-1.fc32.noarch - cannot install the best update candidate for package cockpit-dashboard-232-1.fc32.noarch This is a packaging issue. I've worked around it by removing cockpit-dashboard and then doing a dnf update. If I try again to install cockpit-dashboard (which should give me basically cockpit-bridge since the functionality was moved there), I get: Installing: cockpit-dashboard noarch 216-1.fc32 fedora 200 k Downgrading: cockpit-bridge x86_64 216-1.fc32 fedora 602 k cockpit-system noarch 216-1.fc32 fedora 1.8 M (In reply to Charalampos Stratakis from comment #2) > The new package needs to also provide the name of the old for a clean > upgrade path. See also: > https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or- > replacing-existing-packages > > That conflict is present as well at my machine. Although indeed that could be the missing obsoletes as indicated by the upstream PR. > Apparently "Obsoletes" is not strong enough
Obsoletes is very strong. This indicates a problem with it. What obsoletes what?
Apparently, nothing:
$ repoquery --repo={fedora,updates{,-testing}} --releasever 33 --latest=1 --whatobsoletes cockpit-dashboard
(empty result)
> Apparently, nothing: Yeah, being fixed in https://github.com/cockpit-project/cockpit/pull/15244 . We had it in a "if rhel" branch. FEDORA-2021-0ad93a9b1e has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-0ad93a9b1e FEDORA-2021-0ad93a9b1e has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-0ad93a9b1e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-0ad93a9b1e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-0ad93a9b1e has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. |