Bug 1710759
Summary: | Cannot upgrade from Fedora 29 to 30 (fedora-release-matecompiz, fedora-release-workstation) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Milan Crha <mcrha> |
Component: | fedora-release | Assignee: | Mohan Boddu <mboddu> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 30 | CC: | dennis, jdisnard, jkeating, kellin, kevin, mboddu, pierre.blarre, sgallagh, thrcka, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-16 12:53:09 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: |
Description
Milan Crha
2019-05-16 09:18:47 UTC
See https://fedoraproject.org/wiki/Common_F30_bugs#Conflicts_between_fedora-release_packages_when_installing_package_groups Short version is: you can no longer have two different fedora-release-* packages on the system. Pick the one that best represents how you want the system to report itself and remove the other. Ah, I see, thanks. You may want to change that page and write there that using --allowerasing breaks the system in a way that it cannot boot any more. I just tried it and reproduced bug #1710543 with it (using system-upgrade, not distro-sync, this time). Hi, I'm having a similar problem. Following https://fedoraproject.org/wiki/Common_F30_bugs#Conflicts_between_fedora-release_packages_when_installing_package_groups I've tried: # dnf system-upgrade download --releasever=30 --excludepkg fedora-release-matecompiz But I'm getting the following error: ... Error: Problem: package fedora-release-matecompiz-29-10.noarch requires fedora-release = 29-10, but none of the providers can be installed - problem with installed package fedora-release-matecompiz-29-10.noarch - fedora-release-29-10.noarch does not belong to a distupgrade repository - package fedora-release-matecompiz-30-3.noarch is excluded - package fedora-release-matecompiz-30-1.noarch is excluded (try to add '--skip-broken' to skip uninstallable packages) I'm wondering why "fedora-release-matecompiz-29-10.noarch" isn't excluded by "--excludepkg fedora-release-matecompiz" ? Should I use the --skip-broken option ? Cheers (In reply to pierre.blarre from comment #3) > I'm wondering why "fedora-release-matecompiz-29-10.noarch" isn't excluded by > "--excludepkg fedora-release-matecompiz" ? It is excluded, it is written twice in your output. The problem is that the old package has a dependency on an older version of fedora-release, which is being updated, which would break the excluded package. > Should I use the --skip-broken option ? Rather than that, I suggest to solve the problem manually, which means remove one of the fedora-release-XXXXX packages before doing the upgrade. That's better, because the --skip-broken will not update fedora-release, which is not what you want. You can simply: $ rpm -qa | grep fedora-release pick one of the fedora-release-XXXXX you do not want to keep (I do not know which you've installed, but say for example fedora-release-workstation) and: # dnf remove fedora-release-XXXXX and then continue with the upgrade. (In reply to Milan Crha from comment #4) Thanks, that did it. > > $ rpm -qa | grep fedora-release > Output: fedora-release-notes-28.01-2.fc29.noarch fedora-release-29-10.noarch fedora-release-workstation-29-10.noarch fedora-release-matecompiz-29-10.noarch Then: dnf remove fedora-release-matecompiz-29-10.noarch Then upgrade worked! |