Jira (PUP-1073) Common package name in two different providers

[Stefanos Harhalakis (JIRA)]

Title: Message Title

Stefanos Harhalakis commented on an issue   Re: Common package name in two different providers For the fun of it, here's another case of the same problem: tidy{'etcmail1': path => '/etc/mail', age => '30d', matches => '/etc/sendmail.mc.[0-9]* recurse => 1, } tidy{'etcmail2': path => '/etc/mail', age => '30d', matches => '/etc/sendmail.cf.[0-9]* recurse => 1, } The above causes this: Cannot alias Tidy[xxx] to ["/etc/mail"] at yyy.pp:134; resource ["Tidy", "/etc/mail"] already declared at zzz.pp:107 Obviously the example is an oversimplification of an actual case, but the use case is valid. Add Comment   Puppet / PUP-1073 Common package name in two different providers 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... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.