Skip to content
This repository has been archived by the owner on Aug 28, 2024. It is now read-only.

version installed by gem seems to be well behind this repository #54

Open
rful011 opened this issue Jul 14, 2019 · 4 comments
Open

version installed by gem seems to be well behind this repository #54

rful011 opened this issue Jul 14, 2019 · 4 comments

Comments

@rful011
Copy link

rful011 commented Jul 14, 2019

I have just started using ruby-nessus and I am getting warnings from ruby:
/var/lib/gems/2.3.0/gems/ruby-nessus-1.2.0/lib/nessus/Version2/host.rb:362: warning: Enumerator.new without a block is deprecated; use Object#to_enum
so I went and fixed the source and then went looking for the 'original'. The code here has clearly been reworked substantially from what I got from the gem.

I assume the gem has not been updated so my question is -- what is the best way to use the
up to date version of this module? i.e clearly I uninstall the gem and then where should I clone the repository to (working on ubuntu).

@fwininger
Copy link
Collaborator

I have work on this gem to refactor and enhance the gem last year, but I don't have the access to release the code on rubygems.

@rful011 : you can use directly the last version on github :

gem 'ruby-nessus', git: 'https://github.com/Cyberwatch/ruby-nessus.git' 

@mephux can you release the gems on rubygems.org or give me the right to push a new release.

@rful011
Copy link
Author

rful011 commented Jan 13, 2022

LOL! I see nothing has changed.

Two years on and working on another project and I stumbled over the same problem. Spent some time stuffing around and cursing then spotted this! I have been here before!

@rful011
Copy link
Author

rful011 commented Jan 13, 2022

I found this page helpful in getting the 2.0 beta installed: https://www.stevencampbell.info/Ruby-Nessus/

I don't understand how gem 'ruby-nessus', git: 'https://github.com/Cyberwatch/ruby-nessus.git' is supposed to work because gem expects a command ???

@rful011
Copy link
Author

rful011 commented Jan 13, 2022

hmmm... is it time to rename the gem and clone the repository under a different name. I am not familiar with the terms of the various licenses...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants