On 5 août, 09:11, Ohad Levy <ohadl...@gmail.com> wrote:
> I need to double check this, but from vague memory I remember that if you
> had one rpm that required a package, and if it didn't specify that it
> requires both archs, than it would end up installing the package + 64bit lib
> only and not the 32bit libs.
Indeed. We've had problems in CentOS 5.2 (don't remember the exact yum
version).
Installing "curl-dev" would install both 32/64 packages and we ended
with problems (using 32b libs when building 64b which obviously
failed).
We then used yum's plugin "basearchonly". But with yum 3.2.19 that now
ships with CentOS 5.3 basearchonly seems deprecated/unsupported. But
there's a yum.conf option: multilib_policy=best
" multilib_policy
Can be set to ’all’ or ’best’. All means install all
possible arches for any package you want to install. Therefore yum
install
foo will install foo.i386 and foo.x86_64 on x86_64,
if it is available. Best means install the best arch for this
platform,
only."
Looks like "all" was the default or previous behavior. And "best"
works like yum-basearchonly worked.
Anyway we didn't experience any 32b/64b gotchas since we've set
multilib to "best".
Calimero
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
