Bug 1479864 - Upgrade perl-Net-SSH-Perl to 2.12
Summary: Upgrade perl-Net-SSH-Perl to 2.12
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Net-SSH-Perl
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1546648
Blocks: 1479860
TreeView+ depends on / blocked
 
Reported: 2017-08-09 15:23 UTC by Jitka Plesnikova
Modified: 2018-02-26 15:06 UTC (History)
2 users (show)

Fixed In Version: perl-Net-SSH-Perl-2.14-1.fc28 perl-Net-SSH-Perl-2.14-1.fc29
Clone Of:
Environment:
Last Closed: 2018-02-26 15:06:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1543336 0 unspecified CLOSED please provide missing Fedora 27 Perl modules 2022-03-14 22:21:20 UTC

Internal Links: 1543336

Description Jitka Plesnikova 2017-08-09 15:23:28 UTC 
Latest Fedora delivers 1.42 version. Upstream released 2.12. When you have free time, please upgrade it.

The latest version is required for Net-SFTP-0.12.
Comment 1 Paul Howarth 2017-08-09 15:33:00 UTC 
Net-SSH-Perl 2.x depends on CryptX, which bundles libtomcrypt.

Denis Fateyev did show some interest in packaging CryptX but the discussion seemed to tail off around November last year:

https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/P5AYS75L4ENHGWP4MMYIFZ3GMPLOWE2N/

Unless someone is willing to package CryptX, Net-SSH-Perl will be stuck at 1.42.
Comment 2 Paul Howarth 2018-02-26 15:06:54 UTC 
I have now update perl-Net-SSH-Perl to 2.14 in F-28 and Rawhide, albeit hobbled somewhat due to missing ECC support in perl-CryptX (Bug #1545816).

F-28 build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=25322353

Rawhide build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=25322031

I've tested that I can use the eg/pssh script to access some of my machines but the hobbling process may result in some broken behavior that I haven't spotted.
Note You need to log in before you can comment on or make changes to this bug.