Got this fixed, seems the new box had an old version of rake installed and when I did gem install rake, it did not update the system bin.
On Friday, August 17, 2012 11:16:28 AM UTC-5, llowder wrote: > > > > On Friday, August 17, 2012 10:58:40 AM UTC-5, Justin Stoller wrote: >> >> >> This is RSpec using an old way of initializing Rake. >> see: >> http://stackoverflow.com/questions/6085610/ruby-on-rails-and-rake-problems-uninitialized-constant-rakedsl >> >> for more discussion and possible solutions. >> >> Lemme know if that doesn't work for you. >> >> > I had seen that prior to posting. I have another test VM (which is where > I copied the gems from) where it is working. It has a lot more gems > installed due to some testing I did with foreman on that box. So I know > that the version of the gems isn't the problem. > > The other main difference between the two boxes is the puppet and ubuntu > versions (the problem box is running 10.04 + 2.7.14, while the test Vm > where it works is 12.04 + 2.7.17) > > The Rakefile is the same on both boxes, and it is all done as per: > http://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing/ > > > > >> HTH, >> Justin >> >> -- 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/-/NZWcfy4ZaHcJ. 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.
