Bug 2217166

Summary:	I can't get inxi installed on a RECENT RHEL 9.1 install - it IS installed on a prevrious 9.0 installation from months ago.
Product:	[Fedora] Fedora EPEL	Reporter:	John J. Egan <jje47>
Component:	inxi	Assignee:	Vasiliy Glazov <vascom2>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	awilliam, james.antill, vascom2
Target Milestone:	---	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-01-13 13:43:57 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:

Description John J. Egan 2023-06-24 17:15:38 UTC

Description of problem:
Install of inxi fails due to dependency/version

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. dnf -y install inxi
2.
3.

Actual results:
Error: 
 Problem: conflicting requests
  - nothing provides perl(JSON::XS) needed by inxi-3.3.27-1.el9.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)


Expected results:
working installation

Additional info:

Comment 1 Jaroslav Mracek 2023-06-26 15:36:37 UTC

The issue is reproducible. The package is in EPEL 9 and has broken dependency, therefore the issue is not in DNF. Changing the component to EPEL package because missing dependency cannot be resolved on our side.

Comment 2 Vasiliy Glazov 2023-08-01 09:31:12 UTC

Seems that you need to enable PowerTools repo.

Comment 3 Vasiliy Glazov 2023-10-01 07:35:47 UTC

Is problem still actual?

Comment 4 John J. Egan 2023-10-01 12:56:18 UTC

Not for me anymore - about a month later I got it installed.

Comment 5 Adam Williamson 2024-01-13 02:24:17 UTC

These days when you install epel-release , it prints a message warning that many EPEL packages require the 'codeready' repo and recommending that you turn it on. I don't think there's anything the inxi package can do about this, so it'd probably be best to close the bug. For the record, inxi is among those many EPEL packages that do need the 'codeready' repo, you should follow the recommendation and run `crb enable` to turn it on in order to be able to install inxi from EPEL.

Comment 6 John J. Egan 2024-01-13 13:43:57 UTC

Sometime after filing this bug it began working (hit or miss) for me. I am grateful for this latest piece of info which sheds some light. In accordance with your suggestion I am closing this bug. Thank you.