Bug 2325346

Summary:	nexus: fails to install from epel10
Product:	[Fedora] Fedora EPEL	Reporter:	Carl George 🤠 <carl>
Component:	nexus	Assignee:	Stuart Campbell <stuart>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel10	CC:	stuart
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:	2025-03-06 02:41:38 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:	2318269
Bug Blocks:

Description Carl George 🤠 2024-11-11 23:15:13 UTC

Description of problem:
nexus from EPEL 10 has one or more unresolved dependencies, causing it to be uninstallable.


Version-Release number of selected component (if applicable):
nexus-4.4.3-11.el10_0


How reproducible:
always


Steps to Reproduce:
1. dnf install nexus


Actual results:
Error: 
 Problem: conflicting requests
  - nothing provides mxml needed by nexus-4.4.3-11.el10_0.x86_64 from epel


Expected results:
successful installation


Additional info:
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 1 Fedora Update System 2025-03-05 09:15:23 UTC

FEDORA-EPEL-2025-aa341f0d2d (mxml-3.3.1-8.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-aa341f0d2d

Comment 2 Fedora Update System 2025-03-06 02:41:38 UTC

FEDORA-EPEL-2025-aa341f0d2d (mxml-3.3.1-8.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Carl George 🤠 2025-05-13 00:37:37 UTC

While this was resolved for the EPEL 10.1 repo, it is still uninstallable from the EPEL 10.0 repo.  I went ahead and removed the epel10.0 tag from the nexus-4.4.3-11.el10_0 build to remove it there.