This is also a big problem because I want to also install Rails and the default Ruby version on the OS won't allow me to install that gem... as such once thew newer version of Ruby is installed and Puppet tries to install Rails, it still complains about Rails requiring a higher Ruby version (>=1.8.7).
On Friday, July 6, 2012 12:26:06 AM UTC-7, Benjamin Lei wrote: > > So I have added a config in Puppet to replace my OS's old Ruby version > with a newer one. Unfortunately, it seems that if I run vagrant provision > again (which essentially does a puppet apply), Vagrant (or Puppet) reuses > the same ssh session or bash shell or whatever it is. As such, for my > configurations at least, Puppet keeps on trying to "re-install" the newer > Ruby. How do I make it so that if I do "vagrant provision" it creates a new > ssh session or bash shell (or whatever it is)? Because at the first run, > Puppet will have completely and correctly installed the newer Ruby, and if > I run puppet apply or vagrant provision, it should not rerun the install > for the new Ruby. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/oog82o5hx0kJ. 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.
