Issue #1935 has been updated by immerda.
> It wasn't flatly rejected. My point is we are a cross-platform configuration > management system - we try to avoid catering for every edge case. This isn't > a change to the provider but rather to the type and its a change to the > resource model. This is a big change for one case and makes an exception > that only functions for Red Hat. I was already thinking various time about how we could change the package provider to install/remove more than one package at a time. Personally more because yum is very slow and calling it with a set of packages would speed up a puppet run drastically. However I didn't yet come to a solution/idea which I thought is worth sharing. Noting that this might lead for big changes and might be as well interesting for other package managers like apt-get, aptitude, etc. it might be worth to start a discussion thread about that on the dev list, so we could discuss possible solutions for that. ---------------------------------------- Bug #1935: Unable to handle 2 packages with a circular dependency http://projects.reductivelabs.com/issues/1935 Author: harisekhon Status: Rejected Priority: High Assigned to: Category: Target version: Complexity: Unknown Affected version: 0.24.7 Keywords: When trying to remove 2 packages with circular dependencies on one another, neither is ever removed. This occurs on CentOS 5.2 using the std rpm -e operation that puppet defaults to. The problem is that puppet attempts to remove one package at a time, so it fails on one because of the other, and then when it tries to remove the other it fails on the first. There are 2 possible solutions that I can tell: 1. Make a list of all packages to be removed and remove them all in one go in a single rpm command (although a single package name typo may prevent all other packages from being removed in this case which is not that good) 2. Define a way of specifying that 2 or more packages must be removed simultaneously in one command. If you were to do an rpm -e PackageA PackageB then rpm is smart enough to actually resolve both deps and remove both, but if you only specify one, it will not let you. Examples of packages with this circular dep behaviour on CentOS 5.2 include: ypbind <=> yp-tools ifd-egate <=> pcsc-lite oddjob <=> oddjob-libs ... etc I think a force or a recursive removal through yum should be avoided lest people destroy their systems with cascading package deletions. ---------------------------------------- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
