On Feb 27, 11:28 am, Alan Laird <a...@laird.net> wrote:
> On Feb 23, 3:39 pm, Nathan Powell <nat...@nathanpowell.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"
>
> > What does it "say" if you do:
>
> > sudo yum -q install libstdc++.i386
>
> Yum tells me "Error: Nothing to do" in that case.
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?
> '#yum -y install libstdc++34-3.4.0-1.i386' works without issue.
Part of your problem may be that libstdc++.{i386,x86_64} is not the
same package as libstdc++34.{i386,i686,x86_64}. The latter is
probably a "compatibility library" that provides an _old_ version of
libstdc++ (apparently 3.4.0) on systems whose standard version is
newer (possibly alongside the standard version). I'm guessing based
on naming conventions, however, because there is no such package
distributed from the standard CentOS 5/6 repositories.
If libstdc++34 is the package you really want, then that's what you
should ask Puppet to ensure present. If you ask for a diferent
package, then you should not be surprised when that's the package
Puppet tries to give you.
John
--
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.
