On Thursday, April 3, 2014 10:42:26 AM UTC-5, amogh patel wrote: > > Thanks for your reply John. I read about your first solution which you > posted earlier but I'm trying the second one. > >
If you need both the i686 version and the x86_64 version of that package installed, then you should keep their versions synchronized. If not, then you should remove the unneeded version (presumably the i686 one). You can get Puppet to perform the removal for you in the latter case. If you have two architecture variants of the same library package installed, then you cannot update just one of them unless you first turn off the 'protected_multilib' option in your yum configuration, which I advise you NOT to do. If you must maintain a multilib system (instead of, for instance, a pure x86_64 system), then setting yum's multilib_policy to 'all' really is a good choice. If you don't want to do that, then when you manage a package for which multiple arches are in fact presently installed then you must *avoid*specifying a particular architecture (i.e. exactly the opposite of my (2) above). Failing that, your next best option is to avoid managing library packages directly at all. Instead, let yum install library packages automatically, as needed to satisfy the dependencies of other packages. Like many expert systems, yum works most effectively when you give it high-level tasks and let it work out the low-level details for itself. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/858fb32e-2606-48f0-b51d-da76f9deb382%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
