Bug 2313925

Summary: ddupdate: fails to install from epel10
Product: [Fedora] Fedora EPEL Reporter: Carl George 🤠 <carl>
Component: ddupdateAssignee: Jonathan Wright <jonathan>
Status: CLOSED DEFERRED QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel10CC: davide, epel-packagers-sig, jonathan, leamas.alec, xavier
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-10-22 18:14:29 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: 2319785    
Bug Blocks:    

Description Carl George 🤠 2024-09-21 04:17:07 UTC 
Description of problem:
ddupdate from epel10 has an unresolved dependency, causing it to be uninstallable.


Version-Release number of selected component (if applicable):
ddupdate-0.7.1-12.el10_0


How reproducible:
always


Steps to Reproduce:
1. dnf install ddupdate


Actual results:
Error: 
 Problem: conflicting requests
  - nothing provides python3-keyring needed by ddupdate-0.7.1-12.el10_0.noarch from epel


Expected results:
successful installation
Comment 1 Carl George 🤠 2024-10-21 22:51:06 UTC 
If you think resolving this will take a long time, and would prefer to remove this uninstallable package from EPEL 10 in the meantime, just say so in this ticket and I can untag the build for you.  This won't retire the branch, so as soon as the underlying problem is resolved you can re-publish by creating a new update.
Comment 2 Alec Leamas 2024-10-22 08:32:19 UTC 
Removing this from EPEL 10 is the correct thing to do here. So please untag the build.
Comment 3 Carl George 🤠 2024-10-22 18:14:29 UTC 
I've removed the epel10.0 tag from the ddupdate-0.7.1-12.el10_0 build.  It will be removed from the repo during the next compose.  Once the dependencies become available, it can be republished with a new build.  Alternatively, the epel10 branch can be retired if you have no plans to re-add this package to the repo.