Isn't this already solved with the Puppet 4.x packaging (puppet-agent)? So why insist on installing an old Puppet version instead of a modern one?
Personally I prefer that PuppetLabs is developing new features in Puppet 4.x instead of spending time improving packaging and stuff for Puppet 3.x. On Fri, 29 Jan 2016 at 14:31 Alex Harvey <[email protected]> wrote: > Thanks for the heads up. Anything less than Puppet Labs providing a > working Ruby at yum.puppetlabs.com, or CentOS providing one, feels to me > like a bit of a hack. I've seriously got a customer wanting to ditch > Puppet and go to Ansible because because they just want it to be easy to > install open source Puppet 3. We were burnt by Puppet Omnibus. It just > feels a bit like Puppet's giving us the finger, when all it would take is > someone to stick an RPM on a server. This problem could have been solved > years ago, as the original poster in this thread suggested. > > On Friday, January 29, 2016 at 10:38:29 PM UTC+11, Rob Nelson wrote: > >> Ruby 1.9.3 is available in the Software Collections (SCL) repository. >> Instructions at >> https://digitalchild.info/centos-6-5-and-ruby1-9-3-via-software-collections/ >> . >> >> There may be some side effects for any system utilities that expect 1.8.7 >> but that's a risk you'll have to accept if you're still on EL6, just like >> every other ancient version of software it includes. It does "work" in most >> senses, though. >> >> On Friday, January 29, 2016, Alex Harvey <[email protected]> wrote: >> >>> https://bugs.centos.org/view.php?id=10268 >>> >>> On Friday, January 29, 2016 at 4:15:16 PM UTC+11, Alex Harvey wrote: >>>> >>>> I thought I'd just put it out there that it's the Year of Our Lord >>>> 2016* and CentOS is still installing Ruby 1.8.7, and yum.puppetlabs.com >>>> is still not providing a modern Ruby either. >>>> >>>> Yes, PE provides a Ruby. >>>> Yes, Puppet 4 provides a Ruby. >>>> Yes, Puppet-omnibus can build a Ruby. >>>> Yes, RVM is kinda cool. >>>> Yes, compiling Ruby is kinda fun sometimes. >>>> >>>> But, as a user, I want to type "yum install ruby" and, OMFG, ruby >>>> installs. >>>> >>>> *With apologies to adherents of other religious faiths and proponents >>>> of Lunar and non-Gregorian calendars. >>>> >>>> :) >>>> >>>> On Friday, July 26, 2013 at 1:13:24 AM UTC+10, Christian Flamm wrote: >>>>> >>>>> Hi, >>>>> I'm (using CentOS 6.4 and I'm) suffering from an AFAIU >>>>> performance/design bug (http://projects.puppetlabs.com/issues/20865) >>>>> which (althoughit's not recommended as a work-around) does not occur when >>>>> using Ruby-1.9.3 (Yaeh!) instead of Ruby-1.8.7. I just can't find a >>>>> public, >>>>> well-known, well-maintained repository (I can't find any, actually) that >>>>> offers it as an EL6 RPM. >>>>> >>>>> I know one can install different ruby versions with *rvm*. My >>>>> problems with this approach are (similar issues with compiling from >>>>> source): >>>>> >>>>> - *rvm* and *yum* (the way Ruby is currently installed) are tools >>>>> that AFAIK don't care/know about each other >>>>> - *gem* (I guess I'd have to use *gem *then to install puppet?) >>>>> and *yum* (the way puppet and puppet-server packages are currently >>>>> installed) are tools that AFAIK don't care/know about each other >>>>> - Because not caring/knowing about each other - Can one tool harm >>>>> (e.g. partially override?) software/files installed by the other tool? >>>>> - Which Ruby do I start, when typing *ruby *into a console... same >>>>> for *puppet*. Which of these "rivaling" tools (*rvm* vs. *yum*, >>>>> *gem* vs. *yum) *has control over e.g. $PATH order? >>>>> >>>>> That's why I would prefer a Ruby-1.9.3 RPM that I could install (clean >>>>> update over 1.8.7) which in addition works fine with RPM packages (e.g. >>>>> puppet-server-xxx.el6.noarch.rpm, puppet-xxx.el6.noarch.rpm) from >>>>> yum.puppetlabs.com. >>>>> >>>>> Naive question: Why don't you provide one in yum.puppetlabs.com :-) ? >>>>> >>>>> Christian >>>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Developers" 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-dev/0c859244-321e-4560-ba5e-15ebe2fff962%40googlegroups.com >>> <https://groups.google.com/d/msgid/puppet-dev/0c859244-321e-4560-ba5e-15ebe2fff962%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> -- >> >> Rob Nelson >> [email protected] >> >> -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" 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-dev/69210c5c-3cef-41b5-beef-4cdf2250d94f%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-dev/69210c5c-3cef-41b5-beef-4cdf2250d94f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev/CAAAzDLf9A6%3D%2Brb3%2BnjU15Hp44hFj51CJjQyxO%2BO%3DTVqWSSwrGw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
