Bug 2313905

Summary:	centos-packager: fails to install from epel10
Product:	[Fedora] Fedora EPEL	Reporter:	Carl George 🎩 <carl>
Component:	centos-packager	Assignee:	Davide Cavalca <davide>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel10	CC:	davide, epel-packagers-sig, 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-11-22 02:48:46 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:	2319854, 2319897, 2319899
Bug Blocks:

Description Carl George 🎩 2024-09-21 02:37:43 UTC

Description of problem:
centos-packager from epel10 has missing dependencies, causing it to be uninstallable.


Version-Release number of selected component (if applicable):
centos-packager-0.7.0-15.el10_0


How reproducible:
always


Steps to Reproduce:
1. dnf install centos-packager


Actual results:
Error: 
 Problem: conflicting requests
  - nothing provides rpmlint needed by centos-packager-0.7.0-15.el10_0.noarch from epel
  - nothing provides koji needed by centos-packager-0.7.0-15.el10_0.noarch from epel
  - nothing provides fasjson-client needed by centos-packager-0.7.0-15.el10_0.noarch from epel
  - nothing provides python3-fasjson-client needed by centos-packager-0.7.0-15.el10_0.noarch from epel


Expected results:
successful installation

Comment 1 Xavier Bachelot 2024-10-19 10:08:04 UTC

#2319897 NEW        - mikem - Please branch and build koji for EPEL 10
#2319898 NEW        - epel-packagers-sig.org - Please branch and build bodhi-client for EPEL 10
#2319899 NEW        - extras-orphan - Please branch and build python-fasjson-client for EPEL 10

Comment 2 Carl George 🎩 2024-11-22 02:48:46 UTC

I spoke with Davide in chat, and he agreed that it would be best to untag this build for now to avoid having an uninstallable package in the repo.  I have untagged the build, so it should be removed during the next compose.  The branch is still active, and the package can be republished with a new update as soon as all the deps are available.