To All,
Thanks so much for the input. We have plans on mirroring the
repositories that we need to control the production package versions
and another mirror for testing/development that will contain upstream
versions. The usage of the "ensure => latest" parameter makes sense to
us in this context.
Using "latest" and controlling the repositories yourself is best practice I
believe.
On Nov 16, 2010 2:16 PM, "jcbollinger" wrote:
>
> On Nov 16, 11:03 am, Andy wrote:
>> Also, do you typically create your own mirrors of the repositories to
>> control the repository contents?
>
> I don't know abo
On Nov 16, 11:03 am, Andy wrote:
> Also, do you typically create your own mirrors of the repositories to
> control the repository contents?
I don't know about Luke, but I do. That provides not only control
over the repository contents, but also (for me) much better
performance, as my queries an
Hi Luke,
Thanks for the reply. I was wondering about the underlying
repositories. When I did a "yum list all mysql" I only show the
latest release. I am using the standard repos and mirrors for CentOS
base, epel, extras, updates, addons, and rpmforge.
Assuming I get the repository issue worked o
Hi Andy,
That looks like the mysql RPM with version 5.0.77-4.el5_5.3 no longer
exists in your Yum repository and it's been replaced by
5.0.77-4.el5_5.4.
If you want fine grained control of your RPMs with Puppet you'll also
need to manage your own Yum repo and make sure you control what goes
in, b
