Issue #11887 has been updated by Nick Lewis. Status changed from Re-opened to Rejected
This change is due to #8596 (commit:fb2ffd6879f4c885fe29f70e3cf9bcde89cdc8e9), which fixed a bug where conflicts weren't properly detected when the conflict was between the name of one resource and the title of another (resources are aliased with both their title and their name, hence conflict, but that aliasing behavior wasn't working correctly). This behavior of multiple packages with different providers hasn't ever worked (#1398), so this isn't a regression. ---------------------------------------- Bug #11887: Package with different providers should not violate duplicity https://projects.puppetlabs.com/issues/11887 Author: Hunter Haugen Status: Rejected Priority: Normal Assignee: Daniel Pittman Category: Target version: Affected Puppet version: 2.6.13 Keywords: package, provider Branch: In 2.6.12 this works: package { "mysql-gem": ensure => present, name => 'mysql', provider => 'gem', } package { "mysql": ensure => present, } In 2.6.13 it gives this error: Duplicate definition: Package[mysql] is already defined in file /tmp/packages.pp at line 5; cannot redefine at /tmp/packages.pp:8 on node training.puppetlabs.lan This seems like regression -- 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
