Syntax error in staging_windir.rb about puppet-staging HOT 8 CLOSED

Hi,

I ran into the same issue. 1.7.0 was released to re-instate ruby 1.8.x support
Version 2.x has dropped that support.
In your case i would advise to pin to version 1.7.0

from puppet-staging.

Too bad support on 1.8.x has been dropped. Lot's of modules depend on this staging. We are still on RHEL6 with no way to up Ruby. Well i'm pinning to older versions for now; missing out cool new features.

from puppet-staging.

pin ruby to 1.7.0? Before 2.0.0 of the puppet-staging module, there is 1.0.7, which still has this change, and 1.0.6, which also still has this change. 1.0.5 does not have a release on puppet forge.

from puppet-staging.

@bhundven 1.7.0 was a typo. @electrical was actually thinking of 1.0.7. As far as I can see, this release does contain the fix you need in 6729b2a

from puppet-staging.

What is the plan here? I'm having the same issue on some CentOS-6.8 boxes.

from puppet-staging.

@stefanandres 1.0.7 is available if you need ruby 1.8 support. IIRC it should have all the same features as the latest 2.x release.

from puppet-staging.

Well, and then I will no longer get any updates for future changes. :/

Why is the confine :foo: bar syntax favored instead of confine :foo => :bar (which seems to work with both ruby versions)?

from puppet-staging.

@stefanandres I don't expect there will be much/any more development of this module, so in this case, you won't miss much. New features are being added to the much improved puppet-archive module instead.

Voxpupuli have dropped ruby 1.8 support in all of their modules, but this isn't necessarily a problem for EL6 users.
Have you started your migration to puppet 4 yet? The puppet 4 AIO (all in one) packages come with their own ruby 2.1 and puppet 3 is EOL in 30 days time.

from puppet-staging.