Issue #1398 has been updated by andrew grim.
Is this something that will ever be fixed? If not, what is the reasoning behind it? Telling people to rename their packages isn't a very useful answer when public repositories are being used. ---------------------------------------- Feature #1398: Common package name in two different providers https://projects.puppetlabs.com/issues/1398#change-82938 Author: Lawrence Ludwig Status: Accepted Priority: Normal Assignee: Category: package Target version: Affected Puppet version: 0.24.4 Keywords: package alias Branch: 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 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
