On Apr 18, 2010, at 1:55 AM, Daniel Pittman wrote: >> Any ideas as to why ruby-devel was not able to install properly during first >> run? > > Nope. I can tell you right now that it isn't a puppet problem, though.[1] > > The problem is that puppet executed ... > > /usr/bin/yum -d 0 -e 0 -y install ruby-devel > > ... and yum returned an error, claiming that it couldn't find a dependency of > the package. > > Fix your yum setup and puppet will start working. (Maybe you need something > to run a 'yum update' or something like that?) > > Daniel > > Footnotes: > [1] Technically, it may be puppet *related* problem, since the way puppet > invokes the yum command, or the scheduling of it, may cause the failure > by way of some side-effect.
As a temporary workaround, try adding an entry to install ruby-libs between ruby-gems-install and ruby-devel. I say temporary because this looks like a bug that will cause you other problems down the road if you don't find the root cause. Here's one way to diagnose this. Try running puppet on a new system in debug mode. Then run those same commands yourself on a new system replacing -d 0 -e 0 with -d 8 -e 1. Hopefully someone will have an easier idea. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
