[Puppet Users] Re: Puppet playing badly with Debian etch rubygems

2009-01-29 Thread Marcin Owsiany
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 --

[Puppet Users] Re: Puppet playing badly with Debian etch rubygems

2009-01-20 Thread andrew
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 p

[Puppet Users] Re: Puppet playing badly with Debian etch rubygems

2009-01-20 Thread Robin Lee Powell
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 n

[Puppet Users] Re: Puppet playing badly with Debian etch rubygems

2009-01-20 Thread gary
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 wrote: > Le mardi 20 janvier 2009 à 0

[Puppet Users] Re: Puppet playing badly with Debian etch rubygems

2009-01-20 Thread Nicolas Szalay
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 crea

[Puppet Users] Re: Puppet playing badly with Debian etch rubygems

2009-01-20 Thread gary
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. :) Gary On Jan 20, 3:39 pm, James Turnbull wrote: > -BEGIN PGP SIGNED ME

[Puppet Users] Re: Puppet playing badly with Debian etch rubygems

2009-01-19 Thread James Turnbull
-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 Jam

[Puppet Users] Re: Puppet playing badly with Debian etch rubygems

2009-01-19 Thread Nicolas Szalay
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

[Puppet Users] Re: Puppet playing badly with Debian etch rubygems

2009-01-19 Thread Robin Lee Powell
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

[Puppet Users] Re: Puppet playing badly with Debian etch rubygems

2009-01-19 Thread Luke Kanies
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 *imme