On Friday, July 29, 2016 at 7:48:26 PM UTC-7, François Lafont wrote: > > Hi, > > On 30/07/2016 02:00, Geoff Nichols wrote: > > > Because Ruby 2.1 is approaching end-of-life (upstream bugfix support > ended > > March 2016), we need to move puppet-agent to a more modern Ruby version. > > > > If all goes well with testing, the upcoming puppet-agent 1.6.0 release > will > > include Ruby 2.3.1. > > > > Since the update to Ruby 2.3 is a minor release for Ruby, we're > including > > it in a minor release of puppet-agent. > > > > However, user-installed gems in puppet-agent's gem path will require > > re-installation following the upgrade to puppet-agent 1.6.0. (If you > think > > this will affect you, please let us know how, and we’ll look into it.) > > > > If you have any questions about this, please don’t hesitate to ask. > > 1. So it concerns gems installed via this command: > > /opt/puppetlabs/puppet/bin/gem install $gem_foo > > Is it correct? >
Yes, that's correct. > > > 2. And what about gems installed via this command? > > /opt/puppetlabs/bin/puppetserver gem install $gem_foo > > Is a re-installation after the upgrade needed too? > No, gems installed using Puppet Server's `puppetserver gem install` subcommand use a separate (JRuby) interpreter. Those gems should not be affected and should not require re-installation after the upgrade. > > > Thanks in advance for your help. > François Lafont > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/111d9306-d524-4210-92c5-921b65e036cc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
