Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1893114 - broken dependency in libreoffice-kde prevents clean upgrade to Fedora 33
Summary: broken dependency in libreoffice-kde prevents clean upgrade to Fedora 33
Keywords:
Status: CLOSED DUPLICATE of bug 1888954
Alias: None
Product: Fedora
Classification: Fedora
Component: libreoffice
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-30 08:25 UTC by Enrique Meléndez
Modified: 2020-10-30 09:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-30 09:31:24 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Enrique Meléndez 2020-10-30 08:25:08 UTC 
Description of problem:

Upon upgrade to Fedora 33, a broken dependency in libreoffice-kde prevents upgrade. The message is as follows:

Error: 
 Problem: package libreoffice-kde5-1:6.4.7.2-1.fc32.x86_64 requires libreoffice-core(x86-64) = 1:6.4.7.2-1.fc32, but none of the providers can be installed
  - libreoffice-core-1:6.4.7.2-1.fc32.x86_64 does not belong to a distupgrade repository
  - problem with installed package libreoffice-kde5-1:6.4.7.2-1.fc32.x86_64
(try to add '--skip-broken' to skip uninstallable packages)

Version-Release number of selected component (if applicable):

See above

How reproducible:


Steps to Reproduce:
1. sudo dnf system-upgrade --releasever=33 download

2.
3.

Actual results:

Upgrade stops

Expected results:

Upgrade goes on

Additional info:
Comment 1 Caolan McNamara 2020-10-30 09:31:24 UTC 

*** This bug has been marked as a duplicate of bug 1888954 ***
Note You need to log in before you can comment on or make changes to this bug.