Re: [Puppet Users] [puppet-users] apt and gem package with the same name

2010-12-08 Thread Ricky Ticky
Was this resolved? I'm using 2.6.4 and still can't declare packages with the same package name: package { legacy_chunk: name => 'facter', provider => 'rpm', ensure => absent, } package { gem_chunk: name => 'facter', provider => 'gem', ensure => latest } Thank you. -- You received this me

Re: [Puppet Users] [puppet-users] apt and gem package with the same name

2010-07-09 Thread Peter Meier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>> I have tried this solution as well and it did not work. I may resort >>> to an exec as Patrick suggested. >> >> it will work when we have composite primary keys for resources, I'm not >> sure we will get that in 2.6, but there are definately plans

Re: [Puppet Users] [puppet-users] apt and gem package with the same name

2010-07-09 Thread David Schmitt
On 7/8/2010 4:09 AM, Peter Meier wrote: On 07/07/2010 07:10 PM, hernan wrote: I have tried this solution as well and it did not work. I may resort to an exec as Patrick suggested. it will work when we have composite primary keys for resources, I'm not sure we will get that in 2.6, but there a

Re: [Puppet Users] [puppet-users] apt and gem package with the same name

2010-07-07 Thread James Turnbull
Peter Meier wrote: > On 07/07/2010 07:10 PM, hernan wrote: >> I have tried this solution as well and it did not work. I may resort >> to an exec as Patrick suggested. > > it will work when we have composite primary keys for resources, I'm not > sure we will get that in 2.6, but there are definate

Re: [Puppet Users] [puppet-users] apt and gem package with the same name

2010-07-07 Thread Peter Meier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/07/2010 07:10 PM, hernan wrote: > I have tried this solution as well and it did not work. I may resort > to an exec as Patrick suggested. it will work when we have composite primary keys for resources, I'm not sure we will get that in 2.6, but

Re: [Puppet Users] [puppet-users] apt and gem package with the same name

2010-07-07 Thread hernan
I have tried this solution as well and it did not work. I may resort to an exec as Patrick suggested. thnx.. Hernan On Wed, Jul 7, 2010 at 6:12 AM, Gustavo Soares wrote: > I don't think that it should work. > I have a similar a problem when I want to manage to gems with different > versions.. I

Re: [Puppet Users] [puppet-users] apt and gem package with the same name

2010-07-07 Thread Gustavo Soares
I don't think that it should work. I have a similar a problem when I want to manage to gems with different versions.. I have tried something like this: package { "memcached-0.18.0": name => "memcached", provider => gem, ensure => "0.18.0" } package { "memcached-0.20.0": name => "me

Re: [Puppet Users] [puppet-users] apt and gem package with the same name

2010-07-02 Thread Darren Chamberlain
* hernan [2010/06/30 17:02]: > I'm building a puppet manifest for an Ubuntu machine that needs to > have both of these on it: > > package { "memcached": > provider => gem, > ensure => "0.18.0" > } > > package { "memcached": > provider => apt, > ensure => installed > } I

Re: [Puppet Users] [puppet-users] apt and gem package with the same name

2010-07-01 Thread Patrick Mohr
On Jun 30, 2010, at 5:02 PM, hernan wrote: > I'm building a puppet manifest for an Ubuntu machine that needs to > have both of these on it: > > package { "memcached": >provider => gem, >ensure => "0.18.0" > } > > package { "memcached": >provider => apt, >ensure => installed >

[Puppet Users] [puppet-users] apt and gem package with the same name

2010-07-01 Thread hernan
I'm building a puppet manifest for an Ubuntu machine that needs to have both of these on it: package { "memcached": provider => gem, ensure => "0.18.0" } package { "memcached": provider => apt, ensure => installed } This fails with the following error: err: Could not ret