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 #4846

uninstalling packages gives failed dependencies errors

Added by Benedikt Köppel over 5 years ago. Updated over 5 years ago.

Status:DuplicateStart date:09/27/2010
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Affected Puppet version:0.25.5 Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:



I want to ensure that a few packages are not installed on my machine. I have defined this resource:

    package { [ 'php','php-gd','php-xmlrpc','php-cli','php-common','php-pdo','php-mbstring','php-mysql','php-pgsql' ]:
            ensure => absent

I found, that puppet wants to remove each packet separately. This gives errors such as:

debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -e php-common-5.1.6-27.el5.x86_64'
err: //httpd/Package[php-common]/ensure: change from 5.1.6-27.el5 to absent failed: Execution of '/bin/rpm -e php-common-5.1.6-27.el5.x86_64' returned 1: error: Failed dependencies:
    php-common = 5.1.6-27.el5 is needed by (installed) php-pdo-5.1.6-27.el5.x86_64
    php-common = 5.1.6-27.el5 is needed by (installed) php-mbstring-5.1.6-27.el5.x86_64
    php-common = 5.1.6-27.el5 is needed by (installed) php-xmlrpc-5.1.6-27.el5.x86_64
    php-common = 5.1.6-27.el5 is needed by (installed) php-pgsql-5.1.6-27.el5.x86_64

It would be more convenient if all packages are uninstalled in one run, then the provider could decide how to handle the dependencies in between those packages.

My system:

puppet --version: 0.25.5
ruby --version: ruby 1.8.5 (2006-08-25) [x86_64-linux]
cat /etc/redhat-release: Red Hat Enterprise Linux Server release 5.5 (Tikanga)
yum --version: 3.2.22
rpm --version: RPM version

Best Regards, Benedikt Köppel

Related issues

Duplicates Puppet - Feature #2198: Install multiple package within a single call to the pack... Investigating 04/25/2009


#1 Updated by Peter Meier over 5 years ago

  • Status changed from Unreviewed to Duplicate

this is related to #2198 and can only be fixed if puppet provides a way to group various resources together.

Also available in: Atom PDF