Bug 2027767 - Rex is not installable on epel8 because of missing dependencies
Summary: Rex is not installable on epel8 because of missing dependencies
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: Rex
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dominic Hopf
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2196384
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-30 15:25 UTC by Tuomo Soini
Modified: 2023-10-24 12:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-10-24 12:55:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tuomo Soini 2021-11-30 15:25:07 UTC
Rex-1.13.4-1.el8 depends on perl(Net::SSH2) which is not available so it can't be installed.

Comment 1 Dominic Hopf 2022-06-30 10:59:44 UTC
Hi Tuomo,

thanks very much for reporting this issue and sorry for my delayed response on this. I have no RHEL-based system around to check out if this issue is still present, though. Are you able to verify if the package probably is available in the meanwhile?

Regards,
Dominic

Comment 2 Dominic Hopf 2022-07-08 12:29:17 UTC
As far as I can see the issue here isn't an issue with Rex, but rather an issue that perl-Net-SSH is not present in EPEL8 and EPEL9. I've opened these issues here:

* https://bugzilla.redhat.com/show_bug.cgi?id=2105286
* https://bugzilla.redhat.com/show_bug.cgi?id=2105287

Comment 3 Carl George 🤠 2023-05-08 22:03:52 UTC
The dependency is on perl-Net-SSH2, not perl-Net-SSH.  There needs to be a request for perl-Net-SSH2 in EPEL 8.  This bug should stay open until the issue is resolved, i.e. once Rex installs correctly from EPEL 8.  Once a bug is open to request perl-Net-SSH2 in EPEL 8, it should be marked as blocking this bug.

Comment 4 Dominic Hopf 2023-05-09 06:31:14 UTC
Oh, my fault. Thanks for pointing this out!


Note You need to log in before you can comment on or make changes to this bug.