On Monday, October 29, 2012 4:46:56 AM UTC-5, Jelle B. wrote:
>
> Hi I have seen numerous posts via Google saying this is an issue but not
> found a puppet based solution for it.
>
> Does anyone have an idea how I can make this work ? I do realize I am
> looking at separate versions and was playing with the idea to force a more
> locked down versioning to keep them the same but no idea if I can even do
> this.
>
> below the error :
>
> (/Stage[main]/Libstdc/Package[libstdc++.i686]/ensure) change from absent
> to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install
> libstdc++.i686' returned 1: Error: Protected multilib versions:
> libstdc++-4.4.6-4.el6.i686 != libstdc++-4.4.6-3.el6.x86_64#012 You could
> try using --skip-broken to work around the problem#012 You could try
> running: rpm -Va --nofiles --nodigest
>
> the .pp :
>
> class libstdc {
>
> Class["rhn"]->Class["libstdc"]
>
> package { "libstdc++.i686":
> ensure => installed,
> }
>
> package { "libstdc++":
> ensure => installed,
> }
>
> }
>
>
A setup like that is bound to cause you trouble in Puppet, because Puppet's
yum and rpm Package providers don't recognize the architecture as part of
the resource title. Because Puppet will pass it through to yum, you can,
in some circumstances, get it to install the package that way, but Puppet
will try to do so again on every run because it will not recognize the
package as already installed.
In your particular case, you also have trouble because Puppet manages each
package via a separate yum / rpm / whatever command. If you were manually
doing what you want Puppet to do for you, you would probably name both
packages in one yum command, and it would work.
If you always want the multilib behavior you're asking about, then your
best bet (for several reasons) would be to update your yum configuration to
say so. The setting you are looking for is 'multilib_policy' in the [main]
section of /etc/yum.conf. Set it to "all" (default is "best" in recent
RHEL / CentOS / etc.). Having done that, just manage packages by name
without worrying about architecture. You can and probably should manage
that file via Puppet if you're going to use it to get the behavior you
want; in that case you should set up relationships between your Packages
and that File to ensure that the file is managed first.
On the other hand, you really shouldn't need to worry about this sort of
question if you are making good use of your package management system. Yum
will install appropriate packages for your architecture, and when it does
so it will install the packages for any needed libraries, accounting for
architecture. Only if you throw pre-built but unpackaged software into the
mix do you need to pay attention to installing specific-architecture
packages. So don't do that if you can possibly avoid it.
If necessary, you can often wrap a third-party, binary-only software
distributions into RPMs. Doing so is actually much easier than the
standard approach of building the software from source via the RPM system,
and it gets you a package that is easy to install and remove, and that
declares its dependencies in a way that yum and the RPM system can read and
evaluate (the RPM build system automatically scans the files to install for
library dependencies).
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/-/LfSG5T15AcUJ.
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.
