The Puppet Labs Issue Tracker has Moved:

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using See the following page for information on filing tickets with JIRA:

Bug #16177

Packages with the same name but different provider cannot be installed on the same machine

Added by Giles Westwood over 3 years ago. Updated over 3 years ago.

Status:DuplicateStart date:08/30/2012
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Affected Puppet version: Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:


# Tools required by multiple modules
@package { "system-snmp": ensure => present, name => "snmp",  tag => 'autoapply' }

@package { "ruby-snmp":
    name => "snmp",
    provider => "gem",
    ensure => "1.1.0",
    tag => autoapply,

err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Cannot alias Package[ruby-snmp] to [“snmp”] at /var/lib/puppet/modules/semantico_soe/manifests/virtual_resources/gems.pp:11; resource [“Package”, “snmp”] already defined at /var/lib/puppet/modules/os/manifests/debian/virtual_resources/packages.pp:173 at /var/lib/puppet/modules/semantico_soe/manifests/virtual_resources/gems.pp:11 on node

Related issues

Duplicates Puppet - Bug #1398: Common package name in two different providers Accepted 07/07/2008


#1 Updated by Peter Meier over 3 years ago

  • Status changed from Unreviewed to Duplicate

I’m pretty sure you gonna find an older bug talking about that. I remember that MySQL was the example there.

A trivial search brought up: #1398 and #11887

#2 Updated by Giles Westwood over 3 years ago

Sorry about that, does look spot on for the rubygem and system package conflict that I got. I’ll try and search next time!

Also available in: Atom PDF