Bug 2061761 - Unable to install tito on EPEL9
Summary: Unable to install tito on EPEL9
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: tito
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Devan Goodwin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2160722 (view as bug list)
Depends On: 2052617 2061763 2061765 2061768 2061772
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-08 14:06 UTC by Jakub Kadlčík
Modified: 2023-04-08 15:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-08 15:30:36 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jakub Kadlčík 2022-03-08 14:06:59 UTC 
Description of problem:
There are missing runtime dependencies for tito on EPEL9


Version-Release number of selected component (if applicable):
tito-0.6.20-1.el9.noarch


How reproducible:
Always


Steps to Reproduce:
1. dnf install tito


Actual results:
Error: 
 Problem: conflicting requests
  - nothing provides /usr/bin/cheetah needed by tito-0.6.20-1.el9.noarch
  - nothing provides fedpkg needed by tito-0.6.20-1.el9.noarch
  - nothing provides fedora-packager needed by tito-0.6.20-1.el9.noarch
  - nothing provides python3-blessed needed by tito-0.6.20-1.el9.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)



Expected results:
Tito is expected to work on EPEL9


Additional info:
None
Comment 1 jeff 2023-01-13 13:48:46 UTC 
*** Bug 2160722 has been marked as a duplicate of this bug. ***
Comment 2 Pino Toscano 2023-04-08 07:22:29 UTC 
Jakub: it looks like fedora-packager just hit EPEL 9, and it seems that I can install tito on EPEL 9 now!

If you want to confirm that too, I think it should be enough to consider this done :)
Comment 3 Jakub Kadlčík 2023-04-08 15:30:36 UTC 
You are right Pino, 
works for me :-)

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