On Thursday, July 26, 2012 9:57:27 AM UTC-5, Michael Stanhke wrote: > > Did something else pull that package in as a dependency? >
That is what I'm inclined to think, Matthew's denial notwithstanding. It is at any rate exactly the behavior that would be expected if some other package were installed or updated that required newer versions of the packages in question. Puppet knows about and logs only the package it actually requests. Furthermore, it does not follow from the failure to install the one new package that no other packages were updated in that run. If yum performed dependency resolution successfully and download all the needed packages, then it would have started installs. The requested package will always be installed last, because it depends directly or indirectly on everything else. If one of the installs fails then yum will fail, but any packages that were successfully installed before the failure will remain installed. This is all a good argument for maintaining your own repositories. If you control the packages available for installation then you don't need to worry (as much) about unwanted updates. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/_6LkTpsE3wsJ. 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-users?hl=en.
