[Puppet Users] Re: how to handle this package issue?

Larry Ludwig
2008-07-03T15:25:27Z

alias metatype?  explain?

On Jul 3, 9:21 am, "Evan Hisey" <ehi...@gmail.com>
wrote:
> On Thu, Jul 3, 2008 at 7:50 AM, Larry Ludwig <larry...@gmail.com>
wrote:
>
> > I assume puppet puts all the different package types in the same
> > namespace.  Which is bad, this will prevent issues like the one
> > listed.
>
> > -L
> > --
> > Larry Ludwig
> > Empowering Media
> > 1-866-792-0489 x600
> > Managed and Unmanaged Xen VPSes
> >http://www.hostcube.com/
>
> > On Jul 3, 8:44 am, Larry Ludwig <larry...@gmail.com> wrote:
> >> I have a common package name, that''s in two different
package managers
> >> (one with yum the other with gem)
>
> >>         package { "remove-mysql":
> >>                 name     => "mysql",
> >>                 provider => "yum",
> >>                 ensure   => absent,
> >>         }
>
> >> ---------------------------------------------------------
>
> >>         package { "gem-mysql":
> >>                 name    => "mysql",
> >>                 ensure   => "2.7",
> >>                 provider => gem,
> >>         }
> >> ---------------------------------------------------------
>
> >> I get this error.
>
> >> Jul  3 08:43:34 puppetd[11872]: Could not retrieve catalog:
> >> Puppet::Parser::AST::Resource failed with error ArgumentError:
Cannot
> >> alias Package[gem-mysql] to mysql; resource Package[mysql] already
> >> exists at /etc/puppet/modules/ruby-mysql/manifests/init.pp:11 on
node
>
> >> What''s the work around?
>
> Have you tried to force an alias with the alias metatype?
>
> Evan