Bug #11887

Package with different providers should not violate duplicity

Added by Hunter Haugen 4 months ago. Updated 4 months ago.

Status:Rejected Start date:01/11/2012
Priority:Normal Due date:
Assignee:Daniel Pittman % Done:

0%
Category:-
Target version:-
Affected Puppet version:2.6.13 Branch:
Keywords:package, provider
Votes: 0

Description

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

History

#1
Updated by Daniel Pittman 4 months ago

  • Status changed from Unreviewed to Rejected

We are very unlikely to change the uniqueness criteria here; give the packages different names.

#2
Updated by James Turnbull 4 months ago

  • Status changed from Rejected to Re-opened
  • Assignee set to Daniel Pittman

Is there an explanation for the change though? We seem to havechanged behavior in a point release?

#3
Updated by Nick Lewis 4 months ago

  • 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.

Also available in: Atom PDF