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 1703668 - repoview is not installable in Fedora 30 because of unresolved dependencies
Summary: repoview is not installable in Fedora 30 because of unresolved dependencies
Keywords:
Status: CLOSED DUPLICATE of bug 1701917
Alias: None
Product: Fedora
Classification: Fedora
Component: repoview
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Konstantin Ryabitsev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: https://fedoraproject.org/wiki/Common...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-27 11:45 UTC by Markus Teuber
Modified: 2019-05-30 16:50 UTC (History)
4 users (show)

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

Attachments (Terms of Use)

Description Markus Teuber 2019-04-27 11:45:26 UTC 
Description of problem:
repoview is not installable in Fedora 30 because of unresolved dependencies.
It is a Fedora 29 package in the Fedora 30 repos with unresolved dependencies.


Version-Release number of selected component (if applicable):
repoview-0.6.6-13.fc29.noarch

How reproducible:
dnf install repoview

Steps to Reproduce:
1. Install Fedora 30 (RC 1.2)
2. dnf install repoview

Actual results:
Letzte Prüfung auf abgelaufene Metadaten: vor 0:42:38 am Sa 27 Apr 2019 12:52:56 CEST.
Fehler: 
 Problem: conflicting requests
  - nothing provides python2-kid >= 0.6.3 needed by repoview-0.6.6-13.fc29.noarch
(try to add '--skip-broken' to skip uninstallable packages)

Expected results:
package should be build with the correct dependencies

Additional info:
Comment 1 Adam Williamson 2019-05-30 15:13:10 UTC 
This is because its dependency (python-kid) was auto-retired from F30. I'm not sure if it's correct for something to be auto-retired without things it depends on also being retired, I've asked Miro about this.

There is nothing that can actually be done about this unless python-kid can be revived on the F30 branch...
Comment 2 Miro Hrončok 2019-05-30 16:50:49 UTC 

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