I''m trying to have puppet install a bunch of ruby gems for me, but
I''m
running into problems with a few of them.
This is on CentOS 4.4, ruby 1.8.5 (2006-08-25) [x86_64-linux] and the latest
puppet from svn as of yesterday afternoon.
I have:
package { fastthread:
ensure => "0.6.4.1",
provider => gem,
require => Package["rubygems"],
}
The rubygems package it''s requiring is installed by yum and that works
great.
But here is the problem I run into when I run /etc/init.d/puppet
debug: package provider gem: Executing ''/usr/bin/gem list --local
fastthread''
debug: //pwc01/appserver/Package[fastthread]: Changing ensure
debug: //pwc01/appserver/Package[fastthread]: 1 change(s)
debug: package provider gem: Executing ''/usr/bin/gem install -v
0.6.4.1fastthread''
Then it just hangs for ever.
strace of the gem process shows it''s in this loop:
read(0, 0x2a990ad000, 1024) = ? ERESTARTSYS (To be restarted)
--- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
rt_sigreturn(0x1a) = -1 EINTR (Interrupted system call)
I''m guessing it''s waiting for user input, because when I run
the command
manually it''s asking if I want the ruby or mswin32 version.
I seem to be missing how to specify that I want the ruby version.
Also is there a way to make puppet add --include-dependencies so I
don''t
have to explicitly call out every package?
My poor understanding of the code suggests not.
Thanks!
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
On Mar 13, 2007, at 1:21 PM, Travis Cole wrote:> [...] > I''m guessing it''s waiting for user input, because when I run the > command manually it''s asking if I want the ruby or mswin32 version. > I seem to be missing how to specify that I want the ruby version.I guess there isn''t a way at the moment. It''s pretty ridiculous that it even asks this question, but that''s not your fault. Is there a way to tell gems to take the reasonable, default answer?> Also is there a way to make puppet add --include-dependencies so I > don''t have to explicitly call out every package? > My poor understanding of the code suggests not.I hadn''t thought about it, but yeah, this is a good idea. Should this just always be true? Seems like it should. -- Risk! Risk anything! Care no more for the opinions of others, for those voices. Do the hardest thing on earth for you. Act for yourself. Face the truth. -- Katherine Mansfield --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On 3/22/07, Luke Kanies <luke@madstop.com> wrote:> > On Mar 13, 2007, at 1:21 PM, Travis Cole wrote: > > [...] > > I''m guessing it''s waiting for user input, because when I run the > > command manually it''s asking if I want the ruby or mswin32 version. > > I seem to be missing how to specify that I want the ruby version. > > I guess there isn''t a way at the moment. It''s pretty ridiculous that > it even asks this question, but that''s not your fault.Yeah, I agree. There has been some talk from the gem developers about fixing that, but it hasn''t happened yet. Is there a way to tell gems to take the reasonable, default answer? I haven''t found one yet. My solution was to use gem2rpm and create my own yum repo. That doesn''t work so well for people on other distros or OSs.> Also is there a way to make puppet add --include-dependencies so I > > don''t have to explicitly call out every package? > > My poor understanding of the code suggests not. > > I hadn''t thought about it, but yeah, this is a good idea. > > Should this just always be true? Seems like it should.That would make sense to me. I''m all for things being easier. _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Mar 22, 2007, at 10:02 AM, Travis Cole wrote:> I guess there isn''t a way at the moment. It''s pretty ridiculous that > it even asks this question, but that''s not your fault. > > Yeah, I agree. There has been some talk from the gem developers > about fixing that, but it hasn''t happened yet. > > Is there a way to tell gems to take the reasonable, default answer? > > I haven''t found one yet. My solution was to use gem2rpm and create > my own yum repo. That doesn''t work so well for people on other > distros or OSs.Another possibility would be to run your own local Gem server, that includes all the versions and dependencies. But *not* any of the other versions, or gems for other platforms. That would cause gem to do the right thing. http://rubygems.org/read/chapter/18#page80 This would probably require at least adding the option for the Gem package provider to pick the repository it''s pulling from.> > Also is there a way to make puppet add --include-dependencies so I > > don''t have to explicitly call out every package? > > My poor understanding of the code suggests not. > > I hadn''t thought about it, but yeah, this is a good idea. > > Should this just always be true? Seems like it should. > > That would make sense to me. I''m all for things being easier.Seems like it should always be true to me. Adam
On Mar 22, 2007, at 12:02 PM, Travis Cole wrote:> > On 3/22/07, Luke Kanies <luke@madstop.com> wrote: > Is there a way to tell gems to take the reasonable, default answer? > > I haven''t found one yet. My solution was to use gem2rpm and create > my own yum repo. That doesn''t work so well for people on other > distros or OSs.So you can''t think of an automated way to tell the gems app which package to use? If we can''t get that, then there''s no way I can automate it. -- Life isn''t fair. It''s just fairer than death, that''s all. -- William Goldman --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On 3/24/07, Luke Kanies <luke@madstop.com> wrote:> > On Mar 22, 2007, at 12:02 PM, Travis Cole wrote: > > > > On 3/22/07, Luke Kanies <luke@madstop.com> wrote: > > Is there a way to tell gems to take the reasonable, default answer? > > > > I haven''t found one yet. My solution was to use gem2rpm and create > > my own yum repo. That doesn''t work so well for people on other > > distros or OSs. > > So you can''t think of an automated way to tell the gems app which > package to use? If we can''t get that, then there''s no way I can > automate it.The only thing I can think of is doing things like an expect script would. Or wait until the gem developers fix this. :( _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Mar 24, 2007, at 11:09 PM, Travis Cole wrote:> > The only thing I can think of is doing things like an expect script > would. Or wait until the gem developers fix this. :(Is it filed as a bug? Are they actively planning on fixing it? Seems to me this makes installing gems basically impossible using Puppet right now, right? Seems like the only real option is to support specifying a string to get piped into the stupid gem command. Does anyone else see another way? -- Brand''s Asymmetry: The past can only be known, not changed. The future can only be changed, not known. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com