On Feb 27, 3:57 pm, jcbollinger <john.bollin...@stjude.org> wrote:
> > > On Thu, Feb 23, 2012 at 5:57 PM, AlanLaird<a...@laird.net> wrote:
> > > > I'm trying to write a recipe to install the latest libstdc++ in both
> > > > 32bit and 64bit flavors and running into issues.  Yum only wants to
> > > > install the 64bit version if I do:
>
> > > > yum install libstdc++
>
> > > > If I do something like:
>
> > > > package { "libstdc++.i386" : ensure => latest }
>
> > > > It tells me "nothing to do"
>
> And that says that the package is already installed.  You could verify
> that in a variety of ways, such as "rpm -q libstdc++" or "yum list
> installed libstdc++" or even "yum list installed 'libstdc++*'".  Why
> is "Nothing to do" not an acceptable answer?

The issue I'm chasing is that I need to install a 32bit libstdc++ to
support a vendor supplied rpm and I already have the 64bit libstdc++
installed.  Before today, I was hacking my way around this issue by
installing the 32bit libstdc++ rpm by a package statement that uses
name.version.architecture.  This is was working until one of the
systems in my pool had a newer version of the same name and
architecture which causes puppet to throw this error:

err: /Stage[main]/Lsi6::Management/Package[libstdc++34-3.4.0-1.i386]/
ensure: change from absent to present failed: Execution of '/usr/bin/
yum -d 0 -e 0 -y install libstdc++34-3.4.0-1.i386' returned 1:

Transaction Check Error:
  file /usr/lib/libstdc++.so.6 from install of libstdc+
+34-3.4.0-1.i386 conflicts with file from package libstdc+
+-4.4.6-3.el6.i686

It seems like there must be an elegant way to install the latest of
name.*.architecture where architecture is i386 or i686.

Alan

-- 
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.

Reply via email to