I think you miss the point. I do not need to hand-build Ruby -- it is available from the puppetlabs-deps repo
It is a chicken-egg dilemma with Ruby and Passenger. Passenger depends on the installed version of Ruby. Trying to update Ruby causes a dependency error from Passenger. I tried re-building Passenger from SRPM, but ran into problems. It would be nice if the maintainer of the Passenger RPM's would surface and help out, but ...? If I force Ruby to update to 1.8.7.x, will yum continue to complain about a dependency problem with Passenger or will it re-examine the system and "see" the currently installed version ? On Oct 8, 2012, at 3:13 PM, Jo Rhett wrote: >>> Actually, it's not specified in the source RPM. And just recompiling the >>> source RPM solves the problem. I ran into the same thing, just grabbed the > > On Oct 6, 2012, at 3:39 PM, Dan White wrote: >> Actually, it is. >> >> https://github.com/erikogan/passenger/blob/master/rpm/passenger.spec >> >> ruby_version_patch -- lines 55-67, line 86, and line 238 >> >> It looks for the version that is already installed. > > Saying "use the current version" generally means "not specified" ;-) > Especially when I was responding to your query about what to fix. > >> So how do I update ruby ? > > https://groups.google.com/d/msg/puppet-users/CQTHj9nIYCw/b2Cr7-BxAwkJ > > I am trying to be helpful, but all of this is very google-able. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
