On 10/07/2012 11:28 PM, Sandra Schlichting wrote:
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
> 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
>
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 pac
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 versión
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 that
Hi Chad
* Take a look at the yum versionlock plugin. My life has been much
> simpler since I deployed it. For a while I was "exclude"ing puppet
> and friends in yum.conf, but that was a real pain. The versionlock
> plugin "pins" a package at the version you want, and then you can
> update
- Original Message -
> From: "R.I.Pienaar"
> To: puppet-users@googlegroups.com
> Sent: Wednesday, October 3, 2012 8:25:52 PM
> Subject: Re: [Puppet Users] Puppet 2.7 v 3.0 in the PuppetLabs yum repo
>
>
>
> - Original Message -
> > F
- Original Message -
> From: "jcbollinger"
> To: puppet-users@googlegroups.com
> Sent: Wednesday, October 3, 2012 8:20:38 PM
> Subject: Re: [Puppet Users] Puppet 2.7 v 3.0 in the PuppetLabs yum repo
>
>
>
> On Wednesday, October 3, 2012 9:
On Wednesday, October 3, 2012 9:24:01 AM UTC-5, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > From: "Rilindo Foster" >
> > To: puppet...@googlegroups.com
> > Sent: Wednesday, October 3, 2012 3:02:58 PM
> > Subject: Re: [Pup
full disclosure: I don't use the puppetlabs repos. Below are just some
observations and concerns I wanted to voice.
On Tue, Oct 2, 2012 at 5:36 PM, Michael Stahnke wrote:
> On Tue, Oct 2, 2012 at 1:30 PM, Jeff McCune wrote:
> > On Tue, Oct 2, 2012 at 1:17 PM, Robert Rothenberg
> wrote:
> >> I a
+1
On Wed, Oct 3, 2012 at 9:02 AM, Rilindo Foster wrote:
> I usually explicitly set the $puppetversion in my manifest for my
> environment. Furthermore, I have my own mirror copied from puppet labs repo
> and install it from that location instead. That way, I have control of what
> I push out an
On Wednesday, October 3, 2012 3:51:28 PM UTC+1, Chad Huneycutt wrote:
>
> I agree that folks should manage their repos, but I wanted to throw in
> a couple of thoughts:
>
> * The package name hacks (eg puppet3) are usually done by
> distributions to allow multiple versions of software to co-ex
It might be worth an enhancement request to have Package: ensure => version
call yum versionlock or zypper add-lock if they are present
On Oct 3, 2012 10:55 AM, "Mister Guru" wrote:
>
>
> On 3 October 2012 15:51, Chad Huneycutt wrote:
>
>> I agree that folks should manage their repos, but I want
On 3 October 2012 15:51, Chad Huneycutt wrote:
> I agree that folks should manage their repos, but I wanted to throw in
> a couple of thoughts:
>
> * The package name hacks (eg puppet3) are usually done by
> distributions to allow multiple versions of software to co-exist.
>
I think that we have
I agree that folks should manage their repos, but I wanted to throw in
a couple of thoughts:
* The package name hacks (eg puppet3) are usually done by
distributions to allow multiple versions of software to co-exist.
* Take a look at the yum versionlock plugin. My life has been much
simpler sinc
On 3 October 2012 15:02, Rilindo Foster wrote:
> I usually explicitly set the $puppetversion in my manifest for my
> environment. Furthermore, I have my own mirror copied from puppet labs repo
> and install it from that location instead. That way, I have control of what
> I push out and only upda
- Original Message -
> From: "Rilindo Foster"
> To: puppet-users@googlegroups.com
> Sent: Wednesday, October 3, 2012 3:02:58 PM
> Subject: Re: [Puppet Users] Puppet 2.7 v 3.0 in the PuppetLabs yum repo
>
> I usually explicitly set the $puppetversion in my m
I usually explicitly set the $puppetversion in my manifest for my environment.
Furthermore, I have my own mirror copied from puppet labs repo and install it
from that location instead. That way, I have control of what I push out and
only update when I know that the new version is sound.
So I am
On Tuesday, October 2, 2012 7:36:22 PM UTC-5, Michael Stanhke wrote:
>
> On Tue, Oct 2, 2012 at 1:30 PM, Jeff McCune
> >
> wrote:
> > On Tue, Oct 2, 2012 at 1:17 PM, Robert Rothenberg
> > >
> wrote:
> >> I am using CentOS 6 with the PuppetLabs yum repo from
> >> http://yum.puppetlabs.com
On 2 Oct 2012, at 21:17, Robert Rothenberg wrote:
> I am using CentOS 6 with the PuppetLabs yum repo from
> http://yum.puppetlabs.com
>
> I noticed that today version 3 is available on the repo, so of course, an
> upgrade to Puppet is available.
>
> Ideally, it would have been better if v3 ha
On Wednesday, October 3, 2012 1:36:22 AM UTC+1, Michael Stanhke wrote:
>
> On Tue, Oct 2, 2012 at 1:30 PM, Jeff McCune
> >
> wrote:
> > On Tue, Oct 2, 2012 at 1:17 PM, Robert Rothenberg
> > >
> wrote:
> >> I am using CentOS 6 with the PuppetLabs yum repo from
> >> http://yum.puppetlabs.com
On Tue, Oct 2, 2012 at 1:30 PM, Jeff McCune wrote:
> On Tue, Oct 2, 2012 at 1:17 PM, Robert Rothenberg wrote:
>> I am using CentOS 6 with the PuppetLabs yum repo from
>> http://yum.puppetlabs.com
>>
>> I noticed that today version 3 is available on the repo, so of course, an
>> upgrade to Puppet
On Tue, Oct 2, 2012 at 1:17 PM, Robert Rothenberg wrote:
> I am using CentOS 6 with the PuppetLabs yum repo from
> http://yum.puppetlabs.com
>
> I noticed that today version 3 is available on the repo, so of course, an
> upgrade to Puppet is available.
Yes, this major version update went live on
I am using CentOS 6 with the PuppetLabs yum repo from
http://yum.puppetlabs.com
I noticed that today version 3 is available on the repo, so of course, an
upgrade to Puppet is available.
Ideally, it would have been better if v3 had a different distribution name,
so that systems with v2.7.x are
24 matches
Mail list logo
