Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Newer version of oxidized-script gem #43

Open
codeout opened this issue Jan 31, 2023 · 10 comments
Open

Newer version of oxidized-script gem #43

codeout opened this issue Jan 31, 2023 · 10 comments

Comments

@codeout
Copy link

codeout commented Jan 31, 2023

Hi @ytti, do you have any plan to publish newer version as gem?

oxidized-script 0.6.0 doesn't work along with oxidized 0.28 due to version conflict of "slop" gem.

Thanks,

oxidized-script 0.6.0

s.add_runtime_dependency 'oxidized', '~> 0.25'
s.add_runtime_dependency 'slop', '~> 3.5'

  s.add_runtime_dependency 'oxidized', '~> 0.25'  # covers 0.28.0
  s.add_runtime_dependency 'slop',     '~> 3.5'   # but this conflicts with 4.6

oxidized 0.28.0

https://github.com/ytti/oxidized/blob/835384c6bb3a02896d05c73a1476c054b0856965/oxidized.gemspec#L27

s.add_runtime_dependency 'slop',    '~> 4.6'
@mortzu
Copy link
Collaborator

mortzu commented Apr 14, 2023

@ytti, can you give me permissions in the github project and on rubygems? then I will publish a new gem

@ytti
Copy link
Owner

ytti commented Apr 14, 2023

@mortzu you actually had it on rubygems, I removed them earlier today for three independent reasons, inactivity, another contributor rolled gem for oxidized yesterday and lack of MFA.

I will give @aschaber1 right of first refusal, on thesis that more cooks isn't better for pushing out releases. Should he refuse, I'll set you up.

@mortzu
Copy link
Collaborator

mortzu commented Apr 14, 2023

yeah. thats fine for me

@aschaber1
Copy link
Collaborator

aschaber1 commented Apr 14, 2023

I'm happy either way. I can do the release today, or @mortzu can do it.
I'll propose a GitHub Action on the weekend anyway, that will release ruby gems automatically on merge on master. Then this becomes a non-issue.

@joschi99
Copy link

oxidized version 0.29 is now available

@mortzu
Copy link
Collaborator

mortzu commented Apr 22, 2023

I'm happy either way. I can do the release today, or @mortzu can do it. I'll propose a GitHub Action on the weekend anyway, that will release ruby gems automatically on merge on master. Then this becomes a non-issue.

any news?

@aschaber1
Copy link
Collaborator

ytti/oxidized#2754

My friend created some pipelines which might help us out :)

@cjwbath
Copy link

cjwbath commented Jul 11, 2023

+1 on finishing this off - just did a new gem install and have ended up with:

  • oxidized 0.29.1 polling configs, working fine
  • oxidized-script 0.6.0, using libraries from oxidized 0.26.3 pulled in as dependency, not able to connect to anything via SSH:
oxidized@oxidized:~$ oxs -d -v test.thing 'show run'
unable to connect
/var/lib/gems/3.1.0/gems/oxidized-script-0.6.0/lib/oxidized/script/script.rb:113:in `connect': unable to connect (Oxidized::Script::NoConnection)
        from /var/lib/gems/3.1.0/gems/oxidized-script-0.6.0/lib/oxidized/script/script.rb:92:in `initialize'
        from /var/lib/gems/3.1.0/gems/oxidized-script-0.6.0/lib/oxidized/script/cli.rb:122:in `new'
        from /var/lib/gems/3.1.0/gems/oxidized-script-0.6.0/lib/oxidized/script/cli.rb:122:in `connect'
        from /var/lib/gems/3.1.0/gems/oxidized-script-0.6.0/lib/oxidized/script/cli.rb:37:in `run'
        from /var/lib/gems/3.1.0/gems/oxidized-script-0.6.0/bin/oxs:5:in `<top (required)>'
        from /usr/local/bin/oxs:25:in `load'
        from /usr/local/bin/oxs:25:in `<main>'

Trying to debug that any further is really hard without hacking around in the code (-d and -v flags don't seem to have helped) and I don't want to do that on an old version if the new version is apparently working.

@ahab77
Copy link

ahab77 commented Oct 10, 2023

we have the same problem. With oxidized 0.29.1 the connection works, with oxs or oxidized-script 0.6.0 no connection can be established. Same error as with cjwbath

@Vladyslav78956785786576

Up.

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

No branches or pull requests

8 participants