[Puppet Users] Re: Puppet playing badly with Debian etch rubygems
On Tue, Jan 20, 2009 at 02:05:37AM -0800, gary wrote: I mean that some debgems and deb packages have the same name. If you tried to install them both (like puppet), it could be difficult. Maybe apt has some way to include certain packages from a particular repo man 5 apt_preferences -- Marcin Owsiany mar...@owsiany.pl http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 Every program in development at MIT expands until it can read mail. -- Unknown --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] Re: Puppet playing badly with Debian etch rubygems
Le mardi 20 janvier 2009 à 01:28 -0800, gary a écrit : I think using debgem would possibly make gems more difficult to manage thru Puppet. Even with the gem provider, gems and packages that have the same name (mysql, puppet, ..) conflict. A fix for that sure would be nice. :) Packages created are using the debian naming conventions, so it should not harm. But I'd like to see a free competitor for this system, because to me the idea is nice. -- Nicolas Szalay Administrateur systèmes réseaux -- _ ASCII ribbon campaign ( ) - against HTML email X vCards / \ signature.asc Description: Ceci est une partie de message numériquement signée
[Puppet Users] Re: Puppet playing badly with Debian etch rubygems
I mean that some debgems and deb packages have the same name. If you tried to install them both (like puppet), it could be difficult. Maybe apt has some way to include certain packages from a particular repo like yum. Gary On Jan 20, 5:31 pm, Nicolas Szalay nsza...@qualigaz.com wrote: Le mardi 20 janvier 2009 à 01:28 -0800, gary a écrit : I think using debgem would possibly make gems more difficult to manage thru Puppet. Even with the gem provider, gems and packages that have the same name (mysql, puppet, ..) conflict. A fix for that sure would be nice. :) Packages created are using the debian naming conventions, so it should not harm. But I'd like to see a free competitor for this system, because to me the idea is nice. -- Nicolas Szalay Administrateur systèmes réseaux -- _ ASCII ribbon campaign ( ) - against HTML email X vCards / \ signature.asc 1KViewDownload --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] Re: Puppet playing badly with Debian etch rubygems
On Tue, Jan 20, 2009 at 06:39:53PM +1100, James Turnbull wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nicolas Szalay wrote: Le lundi 19 janvier 2009 à 15:33 -0800, Robin Lee Powell a écrit : OK, so how do I fix it? I think that debgem will be helpfull in a near future : http://debgem.phusion.nl/ Except that it isn't free. [off-topic] Staggeringly un-free, in fact; there's no way I'd ever pay those prices for a service that'll save me maybe half an hour a month, on average. Yeesh. -Robin -- They say: The first AIs will be built by the military as weapons. And I'm thinking: Does it even occur to you to try for something other than the default outcome? -- http://shorl.com/tydruhedufogre http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] Re: Puppet playing badly with Debian etch rubygems
I look a little bit at this error and I believe the root cause is a newer ruby gems trying to check 'specification' on an older rails gem. (or perhaps the opposite) Try an update on the rails gem and see if that helps. One solution on a blog post was to uninstall all the debs and install ruby packages from source. Let us know what seems to work best for you. On Jan 16, 12:39 pm, Robin Lee Powell rlpow...@digitalkingdom.org wrote: To install the ruby-augeas gem, I installed rubygems on Debian etch, which lead to: Setting up libgems-ruby1.8 (0.9.0-5) ... Setting up ruby1.8-dev (1.8.5-4etch4) ... Setting up rubygems (0.9.0-5) ... Before this (I mean *immediately* before this) puppet worked fine exceept for not being able to find a provider for Augeas. After this, though: ec2-www1:/usr/src# puppetd -t Failed to load feature test for rails: private method `specification_version=' called for #Gem::Specification:0xb7e93c04 /usr/lib/ruby/1.8/rubygems/source_index.rb:86:in `load_specification': private method `specification_version=' called for #Gem::Specification:0xb7ae48b0 (NoMethodError) from /usr/lib/ruby/1.8/rubygems/specification.rb:401:in `initialize' from (eval):1:in `new' from (eval):1:in `load_specification' from /usr/lib/ruby/1.8/rubygems/source_index.rb:121:in `eval' from /usr/lib/ruby/1.8/rubygems/source_index.rb:86:in `load_specification' from /usr/lib/ruby/1.8/rubygems/source_index.rb:121:in `load_gems_in' from /usr/lib/ruby/1.8/rubygems/source_index.rb:120:in `each' from /usr/lib/ruby/1.8/rubygems/source_index.rb:120:in `load_gems_in' ... 36 levels... from /usr/local/lib/site_ruby/1.8/puppet/util/settings.rb:724:in `use' from /usr/local/lib/site_ruby/1.8/puppet/network/client/master.rb:197:in `initialize' from /usr/sbin/puppetd:328:in `new' from /usr/sbin/puppetd:328 Installing libgems-ruby1.8 (1.1.1-1~bpo40+1) from etch-backports fixes, but I wanted to mention it in case y'all wanted to fix it in Puppet somehow. -Robin -- They say: The first AIs will be built by the military as weapons. And I'm thinking: Does it even occur to you to try for something other than the default outcome? --http://shorl.com/tydruhedufogrehttp://www.digitalkingdom.org/~rlpowell/***http://www.lojban.org/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] Re: Puppet playing badly with Debian etch rubygems
On Jan 16, 2009, at 1:39 PM, Robin Lee Powell wrote: To install the ruby-augeas gem, I installed rubygems on Debian etch, which lead to: Setting up libgems-ruby1.8 (0.9.0-5) ... Setting up ruby1.8-dev (1.8.5-4etch4) ... Setting up rubygems (0.9.0-5) ... Before this (I mean *immediately* before this) puppet worked fine exceept for not being able to find a provider for Augeas. After this, though: ec2-www1:/usr/src# puppetd -t Failed to load feature test for rails: private method `specification_version=' called for #Gem::Specification:0xb7e93c04 /usr/lib/ruby/1.8/rubygems/source_index.rb:86:in `load_specification': private method `specification_version=' called for #Gem::Specification:0xb7ae48b0 (NoMethodError) from /usr/lib/ruby/1.8/rubygems/specification.rb:401:in `initialize' from (eval):1:in `new' from (eval):1:in `load_specification' from /usr/lib/ruby/1.8/rubygems/source_index.rb:121:in `eval' from /usr/lib/ruby/1.8/rubygems/source_index.rb:86:in `load_specification' from /usr/lib/ruby/1.8/rubygems/source_index.rb:121:in `load_gems_in' from /usr/lib/ruby/1.8/rubygems/source_index.rb:120:in `each' from /usr/lib/ruby/1.8/rubygems/source_index.rb:120:in `load_gems_in' ... 36 levels... from /usr/local/lib/site_ruby/1.8/puppet/util/settings.rb: 724:in `use' from /usr/local/lib/site_ruby/1.8/puppet/network/client/ master.rb:197:in `initialize' from /usr/sbin/puppetd:328:in `new' from /usr/sbin/puppetd:328 Installing libgems-ruby1.8 (1.1.1-1~bpo40+1) from etch-backports fixes, but I wanted to mention it in case y'all wanted to fix it in Puppet somehow. This is unfortunately a rubygems issue, not a Puppet issue, and because of how rubygems are (stupidly) written, we have to require rubygems in case any of our dependencies are installed that way. -- The people who are regarded as moral luminaries are those who forego ordinary pleasures themselves and find compensation in interfering with the pleasures of others. -- Bertrand Russell - Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] Re: Puppet playing badly with Debian etch rubygems
On Mon, Jan 19, 2009 at 02:08:30PM -0600, Luke Kanies wrote: On Jan 16, 2009, at 1:39 PM, Robin Lee Powell wrote: To install the ruby-augeas gem, I installed rubygems on Debian etch, which lead to: Setting up libgems-ruby1.8 (0.9.0-5) ... Setting up ruby1.8-dev (1.8.5-4etch4) ... Setting up rubygems (0.9.0-5) ... Before this (I mean *immediately* before this) puppet worked fine exceept for not being able to find a provider for Augeas. After this, though: ec2-www1:/usr/src# puppetd -t Failed to load feature test for rails: private method `specification_version=' called for #Gem::Specification:0xb7e93c04 /usr/lib/ruby/1.8/rubygems/source_index.rb:86:in `load_specification': private method `specification_version=' called for #Gem::Specification:0xb7ae48b0 (NoMethodError) from /usr/lib/ruby/1.8/rubygems/specification.rb:401:in `initialize' from (eval):1:in `new' from (eval):1:in `load_specification' from /usr/lib/ruby/1.8/rubygems/source_index.rb:121:in `eval' from /usr/lib/ruby/1.8/rubygems/source_index.rb:86:in `load_specification' from /usr/lib/ruby/1.8/rubygems/source_index.rb:121:in `load_gems_in' from /usr/lib/ruby/1.8/rubygems/source_index.rb:120:in `each' from /usr/lib/ruby/1.8/rubygems/source_index.rb:120:in `load_gems_in' ... 36 levels... from /usr/local/lib/site_ruby/1.8/puppet/util/settings.rb: 724:in `use' from /usr/local/lib/site_ruby/1.8/puppet/network/client/ master.rb:197:in `initialize' from /usr/sbin/puppetd:328:in `new' from /usr/sbin/puppetd:328 Installing libgems-ruby1.8 (1.1.1-1~bpo40+1) from etch-backports fixes, but I wanted to mention it in case y'all wanted to fix it in Puppet somehow. This is unfortunately a rubygems issue, not a Puppet issue, and because of how rubygems are (stupidly) written, we have to require rubygems in case any of our dependencies are installed that way. OK, so how do I fix it? -Robin -- They say: The first AIs will be built by the military as weapons. And I'm thinking: Does it even occur to you to try for something other than the default outcome? -- http://shorl.com/tydruhedufogre http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] Re: Puppet playing badly with Debian etch rubygems
Le lundi 19 janvier 2009 à 15:33 -0800, Robin Lee Powell a écrit : OK, so how do I fix it? I think that debgem will be helpfull in a near future : http://debgem.phusion.nl/ -- Nicolas Szalay Administrateur systèmes réseaux -- _ ASCII ribbon campaign ( ) - against HTML email X vCards / \ signature.asc Description: Ceci est une partie de message numériquement signée
[Puppet Users] Re: Puppet playing badly with Debian etch rubygems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nicolas Szalay wrote: Le lundi 19 janvier 2009 à 15:33 -0800, Robin Lee Powell a écrit : OK, so how do I fix it? I think that debgem will be helpfull in a near future : http://debgem.phusion.nl/ Except that it isn't free. Regards James Turnbull - -- Author of: * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) * Hardening Linux (http://www.amazon.com/gp/product/159059/) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJdX/J9hTGvAxC30ARAn1BAJwJmG0P/dkZhevbbzGgtq4Bn4twSACfcpGh 5vUd0VgVBtEIu2c0v2C0N1A= =a0C/ -END PGP SIGNATURE- --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
