[Puppet Users] Re: Rubygems 2.0.0 removed argument

2013-05-16 Thread Ben Polinsky
Is there a fix/workaround/patch for this? On Monday, February 25, 2013 12:31:24 PM UTC-5, matthias wrote: > > I recently upgraded one of our puppet agent servers to use rubygems 2.0.0. > When I run 'puppet agent --test' after the upgrade it complains that there > is an invalid option with using

[Puppet Users] Re: Rubygems 2.0.0 removed argument

2013-02-26 Thread matthias
Looks like there is a bug report for it. http://projects.puppetlabs.com/issues/19140 On Monday, February 25, 2013 9:31:24 AM UTC-8, matthias wrote: > > I recently upgraded one of our puppet agent servers to use rubygems 2.0.0. > When I run 'puppet agent --test' after the upgrade it complains th

[Puppet Users] Re: Rubygems 2.0.0 removed argument

2013-02-25 Thread Reginald Choudari
We are seeing the same issue with our automated deployment of puppetmaster. We are using 'puppetlabs-passenger' install passenger, and we get the same issue. Looks like the gem provider has deprecated arguments; AFAIK --include-dependencies has become default for gem install. On Monday, Februar

[Puppet Users] Re: Rubygems 2.0.0 removed argument

2013-02-25 Thread Reginald Choudari
We are seeing the same issue with our automated deployment of puppetmaster. We are using 'puppetlabs-passenger' install passenger, and we get the same issue (See below). Looks like the gem provider has deprecated arguments; AFAIK --include-dependencies has become default for gem install. Notice