Bug 2170558

Summary: FTI for python3-stevedore on epel8
Product: [Fedora] Fedora EPEL Reporter: Davide Cavalca <davide>
Component: python-stevedoreAssignee: Dan Prince <dprince>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel8CC: apevec, dprince, mrunge, openstack-sig
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-stevedore-3.5.0-4.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-25 05:07:10 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:
Bug Depends On:    
Bug Blocks: 1844523    

Description Davide Cavalca 2023-02-16 17:30:40 UTC
Problem: conflicting requests
  - nothing provides python3-importlib-metadata >= 1.7.0 needed by python3-stevedore-3.5.0-3.el8.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Comment 1 Davide Cavalca 2023-02-16 17:40:12 UTC
Put up https://src.fedoraproject.org/rpms/python-stevedore/pull-request/4 for this

Comment 2 Fedora Update System 2023-02-17 08:58:03 UTC
FEDORA-EPEL-2023-6a0ac4c368 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-6a0ac4c368

Comment 3 Fedora Update System 2023-02-18 01:36:38 UTC
FEDORA-EPEL-2023-6a0ac4c368 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-6a0ac4c368

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2023-02-25 05:07:10 UTC
FEDORA-EPEL-2023-6a0ac4c368 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.