On 10/03/2012 08:38 PM, Aaron Russo wrote:
Personally, I would have liked to see a separate repo for each version
of puppet (so that users of 2.6.x, 2.7.x and 3.0.x could continue to
receive the latest and greatest for their version). But I also don't
have to manage the thing, so I respect
Well, in many enterprise distro having different name and, possibly,
no conflicting path for a complex package is a common option. In
rhel5 for example exists samba package for samba 3.0.x and samba3x for
samba 3.x , and samba it is often a critical package and the change
between different
Hello Stefan,
Yes, I am using Puppet 3.0.0 and RHEL 6.3.
According to the Puppetlabs site, 'purged' should be supported with 'yum'
in the latest version of Puppet:
http://docs.puppetlabs.com/references/latest/type.html#package
As 3.0 is a major release, and two versions (and two years)
Sorry to burst you bubble
The puppet backend has been 'broken' (intentionally?)
- https://projects.puppetlabs.com/issues/16321
-
https://mail.google.com/mail/u/1/?ui=2shva=1#search/label%3Apuppet-users+pienaar/13a168982ad38854
Lots needs fixing...
Zipkid (Stefan)
On Fri, Oct 5, 2012 at
On 10/07/2012 07:30 PM, devzero2000 wrote:
Well, in many enterprise distro having different name and, possibly,
no conflicting path for a complex package is a common option. In
rhel5 for example exists samba package for samba 3.0.x and samba3x for
samba 3.x , and samba it is often a critical
I know for that practice, but the problem is that it makes upgrade from
samba to samba3x packages a problem. So I would rather avoid that with
the puppet. And if you know how to add puppetlabs repo to yum, then
you'll know how to choose what version repo to use. Just take a look at
You could change the interaction in the script so it accepts command
line options.
Then it would be easy to manage with puppet.
On 5 October 2012 16:55, Jon Skarpeteig jon.skarpet...@gmail.com wrote:
The script is several thousand lines of code. Definitely not easier
than Guzman Braso's
