Bug 1710759 - Cannot upgrade from Fedora 29 to 30 (fedora-release-matecompiz, fedora-release-workstation)
Summary: Cannot upgrade from Fedora 29 to 30 (fedora-release-matecompiz, fedora-releas...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-release
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mohan Boddu
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-16 09:18 UTC by Milan Crha
Modified: 2019-06-10 08:27 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-16 12:53:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Milan Crha 2019-05-16 09:18:47 UTC
I tried to upgrade from Fedora 29 to Fedora 30 and it fails on package conflicts. One problem being fedora-release packages (the other is bug #1710756). The terminal output:

# dnf system-upgrade download --refresh --releasever=30
Before you continue ensure that your system is fully upgraded by running "dnf --refresh upgrade". Do you want to continue [y/N]: y
Fedora Modular 30 - x86_64                    25 kB/s |  25 kB     00:00    
Fedora Modular 30 - x86_64 - Updates          21 kB/s |  23 kB     00:01    
Fedora Modular 30 - x86_64 - Updates          92 kB/s | 236 kB     00:02    
Fedora 30 - x86_64 - Updates                  24 kB/s |  22 kB     00:00    
Fedora 30 - x86_64                            34 kB/s |  25 kB     00:00    
Error: 
.....
 Problem 2: package fedora-release-matecompiz-30-1.noarch conflicts with system-release provided by fedora-release-workstation-30-1.noarch
  - package fedora-release-workstation-30-1.noarch conflicts with system-release provided by fedora-release-matecompiz-30-1.noarch
  - problem with installed package fedora-release-workstation-29-10.noarch
  - problem with installed package fedora-release-matecompiz-29-10.noarch
  - fedora-release-workstation-29-10.noarch does not belong to a distupgrade repository
  - fedora-release-matecompiz-29-10.noarch does not belong to a distupgrade repository
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)

Comment 1 Stephen Gallagher 2019-05-16 12:53:09 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.

Comment 2 Milan Crha 2019-05-16 13:36:18 UTC
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).

Comment 3 pierre.blarre 2019-06-08 08:32:20 UTC
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

Comment 4 Milan Crha 2019-06-10 07:39:56 UTC
(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.

Comment 5 pierre.blarre 2019-06-10 08:27:02 UTC
(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!


Note You need to log in before you can comment on or make changes to this bug.