Bug 754324 - Upgrade to latest rubygem-net-ssh
Summary: Upgrade to latest rubygem-net-ssh
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-net-ssh
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Shreyank Gupta
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-16 06:46 UTC by Bohuslav "Slavek" Kabrda
Modified: 2012-06-04 08:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-05 12:05:55 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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. :-)
Note You need to log in before you can comment on or make changes to this bug.