Managing two versions of a package via yum

[Steve Jahl]

Hi,

I'm in a situation where I need to install/manage both the 32-bit and 64-bit versions of a package. Anyone have any tips on doing this? What I've got now, is something like this:

class install32 {
package { 'freetype.i686':
ensure => latest,
require => Class['install64'],
}
}

class install64 {
package { 'freetype.x86_64':
ensure => latest,
}
}

What happens, is when a newer version of the 64-bit version becomes available, it tries to install it, and I see an error like this:
> err: /Stage[main]/Programs::Install64/Package[freetype.x86_64]/ensure: change from 2.3.11-6.el6_1.8 to 0:2.3.11-6.el6_2.9 failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install freetype.x86_64' returned 1: Error: Protected multilib versions: freetype-2.3.11-6.el6_2.9.x86_64 != freetype-2.3.11-6.el6_1.8.i686

What I gather, is that it's not letting me update the 64-bit one, since it wants the 32 and 64-bit versions to match.

I've tried ONLY managing the 32-bit version, to see if if will install the 64-bit one as a dependency for me, but I end up seeing the same multilib error, just in the reverse direction :(

Any help getting me back on track is appreciated.

Thanks,
-Steve

[Steve Traylen]

Who is releasing 32 bit and 64 bit packages out of step? They have to released at the same time else you see the problems you are seeing.

not a puppet problem, a vanilla yum or rpm also fails with this.

Steve.

[Steve Jahl]

On May 16, 2012, at 7:18 PM, Steve Traylen wrote:
>
> not a puppet problem, a vanilla yum or rpm also fails with this.
> Steve.
>

That's what I figured. Found this problem only on freshly kickstarted systems. So, during the kickstart, the package was being installed from the 'base' repo, and then on the first puppet run, it was being installed from the 'updates' repo, and the versions were mismatched.

Enabled the updates repo during the install, looks like I'm good now.

-Steve