Jira (PUP-10394) puppet cannot handle same package name with different providers

[Josh Cooper (Jira)]

Title: Message Title

Josh Cooper commented on PUP-10394   Re: puppet cannot handle same package name with different providers This issue should already be supported, see PUP-1073 In PUP-3721 (fixed in 6.13.0), puppet resource package now emits the provider that was used, to avoid naming collisions. You can achieve the same effect in 5.5.x using puppet resource package --param provider. In order to manage two packages with the same name, you have to specify the provider for both resources, which I think is why this fails: root@sleek-clergymen:~# cat a.pp package { 'ssh-import-id': ensure => '3.21', provider => 'pip', } package { 'ssh-import-id': ensure => '3.21-0ubuntu1', } I don't think puppet will generate the composite key for the resource if the provider is unspecified, and it picks the most suitable provider. See also https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/package/common_package_name_in_different_providers.rb Add Comment   This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.351401.1585313546000.23177.1585345680199%40Atlassian.JIRA.