[Puppet-dev] Announce: Facter 2.0.1-rc2 Now Available.

2014-03-12 Thread Ryan McKern
*Facter 2.0.1-rc2* *Pre-release *RC2: March 12, 2014. *Facter 2.0.1-rc2 Downloads* Source: https://downloads.puppetlabs.com/facter/facter-2.0.1-rc2.tar.gz Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For inf

[Puppet-dev] Notes from the March 12th PR triage

2014-03-12 Thread Adrien Thebo
Joined: Adrien, Andy, Charlie, Dominic Cleal, Josh C, Peter, Rob, Joshua P >From last week: Puppet: 2276: Remove debian as provider for ubuntu. No response from contributor, we will fix ourselves. - Finch to grab this week 2247: Purging ssh keys. Still want to do this for 3.6 - Andy merged, Ch

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

2014-03-12 Thread Trevor Vaughan
I just realized that there's another way around this. It's not so glamorous as fixing the type, but it would work. Just create new types that inherit the package type and hard code the provider. package_yum package_gem etc This would probably be pretty quick work overall and, of course, elim

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

2014-03-12 Thread Pedro Côrte-Real
On Wed, Mar 12, 2014 at 6:35 PM, John Bollinger wrote: > No, that's not really a difference at all. 'command' is the namevar of the > Exec type (it has no 'name' property), and 'name' is the namevar of Package. > It is the fact that 'name' is the namevar of Package that makes the package > versio

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

2014-03-12 Thread John Bollinger
On Tuesday, March 11, 2014 4:23:33 PM UTC-5, Pedro Côrte-Real wrote: > > On Tue, Mar 11, 2014 at 5:29 PM, Andy Parker > > > wrote: > > Personally, I would be ok with yet another hack in puppet 3 to handle > this > > issue since it has been coming up so often and since I also don't know a >

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

2014-03-12 Thread Thomas Linkin
I agree with Adrien. I think the solution will be something with a benefit for the entire RAL. The thought I have is of a solution that preserves the original behavior of having a resource type auto-discover it’s preferred provider on a system. So in this case, we could allow one resource per

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

2014-03-12 Thread David Schmitt
On 2014-03-12 02:13, Trevor Vaughan wrote: If possible, I would love to see this done without a composite namevar. The issue is that youre going to start ending up with variables *everywhere* to figure out what youre actually installing. I'm not fully convinced that this is actually true. I'v