You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest version of rack isn't installable on puppet's ruby 2.1.9.
Up until now, this wasn't a problem as the sinatra gem got installed first and it had a dependency on rack ~> 1.5. (We may as well remove
Sinatra 2.0.0 got released yesterday. It depends on the newer rack. rack ~> 2.0, so we now get
Error: Execution of '/opt/puppetlabs/puppet/bin/gem install --no-rdoc --no-ri sinatra' returned 1: ERROR: Error installing sinatra:
rack requires Ruby version >= 2.2.2.
Error: /Stage[main]/R10k::Webhook::Package/Package[sinatra]/ensure: change from absent to present failed: Execution of '/opt/puppetlabs/puppet/bin/gem install --no-rdoc --no-ri sinatra' returned 1: ERROR: Error installing sinatra:
rack requires Ruby version >= 2.2.2.
Due to the if !defined, wrapping the installation of sinatra, this is easy enough to work around in my profile. We should probably fix the issue in the module though. Is it ok to change
That should be okay, but let's parameterize it with something that defaults to '1.4.8', in case someone wants to provide a specific lower version number.
Re: L14-20, can that be removed? If that's a dependency, seems like the gem provider will install it automatically.
When puppet gets around to 14-20 it has nothing to do since rack is already installed (as a sinatra dependency). Had this not been the case, the module would have been failing since last June (when rack 2.0 came out).
The latest version of rack isn't installable on puppet's ruby 2.1.9.
Up until now, this wasn't a problem as the sinatra gem got installed first and it had a dependency on
rack ~> 1.5
. (We may as well removepuppet-r10k/manifests/webhook/package.pp
Lines 14 to 20 in 1d0c344
Sinatra 2.0.0 got released yesterday. It depends on the newer rack.
rack ~> 2.0
, so we now getDue to the
if !defined
, wrapping the installation of sinatra, this is easy enough to work around in my profile. We should probably fix the issue in the module though. Is it ok to changeto
??
The text was updated successfully, but these errors were encountered: