Bug 754324

Summary: Upgrade to latest rubygem-net-ssh
Product: [Fedora] Fedora Reporter: Bohuslav "Slavek" Kabrda <bkabrda>
Component: rubygem-net-sshAssignee: Shreyank Gupta <shreyankg>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: rpms, shreyankg
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-05 12:05:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Bohuslav "Slavek" Kabrda 2011-11-16 06:46:32 UTC
Hi,
would it be possible to upgrade to the newest version? I need at least 2.1.3 for new version of rubygem-fog (1.1.1) in rawhide.
Thank you.

Comment 1 Bohuslav "Slavek" Kabrda 2011-11-28 07:15:52 UTC
Ping, are you still maintaining this package Shreyank?

Comment 2 Shreyank Gupta 2011-12-04 16:01:25 UTC
Hi,
Sorry for the delay.

I have updated rubygem-net-ssh to its latest version (2.2.1) in F17. http://koji.fedoraproject.org/koji/taskinfo?taskID=3561310

Comment 3 Bohuslav "Slavek" Kabrda 2011-12-05 06:31:33 UTC
Great, thank you.

Comment 4 Jonas Courteau 2012-06-04 04:03:20 UTC
Hello:

Would it be possible to upgrade this package to 2.2.2 or higher for rawhide?  It's a requirement for rubygem-chef, which I'm working on packaging.

Note that the upstream seems to be iterating pretty rapidly right now...

Also please let me know if I should have created a new ticket.  Thanks!

Comment 5 Shreyank Gupta 2012-06-04 08:48:28 UTC
(In reply to comment #4)
> Hello:
> 
> Would it be possible to upgrade this package to 2.2.2 or higher for rawhide?
> It's a requirement for rubygem-chef, which I'm working on packaging.
> 
> Note that the upstream seems to be iterating pretty rapidly right now...
> 
> Also please let me know if I should have created a new ticket.  Thanks!

Yes, this bug is closed. Please create a new bug. :-)