Bug #3390
closedNo answer for 32 bit packages on a 64 bit CentOS system
Description
I get "no answer" when installing 32 bit packages on a 64 bit CentOS system. 64 Bit packages install fine.
Example given:
compat-libf2c-34 No action required for RPM package compat-libf2c-34 with policy: add Success
compat-libf2c-34.i386 No answer
compat-libstdc++-33 No action required for RPM package compat-libstdc++-33 with policy: add Success
compat-libstdc++-33.i386 No answer
libidn.i386 No answer
libsane-hpaio No action required for RPM package libsane-hpaio with policy: add Success
libXaw No action required for RPM package libXaw with policy: add Success
libXmu.i386 No answer
libXp No action required for RPM package libXp with policy: add Success
libXp.i386 No answer
libXpm.i386 No answer
mesa-libGLU.i386 No action required for RPM package mesa-libGLU.i386 with policy: add Success
openmotif No action required for RPM package openmotif with policy: add Success
openmotif.i386 No answer
openmotif22 No action required for RPM package openmotif22 with policy: add Success
openmotif22.i386 No answer
Kind regards
Files
Updated by Dennis Cabooter over 11 years ago
Example given is scrambled. Below I'll add it as preformatted text:
compat-libf2c-34 No action required for RPM package compat-libf2c-34 with policy: add Success compat-libf2c-34.i386 No answer compat-libstdc++-33 No action required for RPM package compat-libstdc++-33 with policy: add Success compat-libstdc++-33.i386 No answer libidn.i386 No answer libsane-hpaio No action required for RPM package libsane-hpaio with policy: add Success libXaw No action required for RPM package libXaw with policy: add Success libXmu.i386 No answer libXp No action required for RPM package libXp with policy: add Success libXp.i386 No answer libXpm.i386 No answer mesa-libGLU.i386 No action required for RPM package mesa-libGLU.i386 with policy: add Success openmotif No action required for RPM package openmotif with policy: add Success openmotif.i386 No answer openmotif22 No action required for RPM package openmotif22 with policy: add Success openmotif22.i386 No answer
Updated by Dennis Cabooter over 11 years ago
Hereby I send you the CFengine promise file.
Updated by Dennis Cabooter over 11 years ago
What I see in the CFengine logs is the following. It seems the same report is sent for all packages in the same directive. In this example only compat-libstdc++-33.i386 has a succes status.
Q:yum y install compa ...:Loaded plugins: fastestmirror> Command related to promiser "compat-libstdc++-33.i386" returned code defined as promise kept (0)
Q:yum -y install compa ...:Loading mirror speeds from cached hostfile
Q:yum -y install compa ...: * addons: centos.crazyfrogs.org
Q:yum -y install compa ...: * base: centos.crazyfrogs.org
Q:yum -y install compa ...: * elrepo: elrepo.org
Q:yum -y install compa ...: * extras: centos.crazyfrogs.org
Q:yum -y install compa ...: * rpmforge: apt.sw.be
Q:yum -y install compa ...: * updates: centos.crazyfrogs.org
Q:yum -y install compa ...:Setting up Install Process
Q:yum -y install compa ...:Package compat-libstdc++-33-3.2.3-61.i386 already installed and latest version
Q:yum -y install compa ...:Nothing to do
Q:yum -y install compa ...:
Q:yum y install compa ...:Loaded plugins: fastestmirror> Command related to promiser "compat-libstdc++-33.i386" returned code defined as promise kept (0)
Q:yum -y install compa ...:Loading mirror speeds from cached hostfile
Q:yum -y install compa ...: * addons: centos.crazyfrogs.org
Q:yum -y install compa ...: * base: centos.crazyfrogs.org
Q:yum -y install compa ...: * elrepo: elrepo.org
Q:yum -y install compa ...: * extras: centos.crazyfrogs.org
Q:yum -y install compa ...: * rpmforge: apt.sw.be
Q:yum -y install compa ...: * updates: centos.crazyfrogs.org
Q:yum -y install compa ...:Setting up Install Process
Q:yum -y install compa ...:Package compat-libstdc++-33-3.2.3-61.x86_64 already installed and latest version
Q:yum -y install compa ...:Nothing to do
Q:yum -y install compa ...:
Q:yum y install libid ...:Loaded plugins: fastestmirror> Command related to promiser "compat-libstdc++-33.i386" returned code defined as promise kept (0)
Q:yum -y install libid ...:Loading mirror speeds from cached hostfile
Q:yum -y install libid ...: * addons: centos.crazyfrogs.org
Q:yum -y install libid ...: * base: centos.crazyfrogs.org
Q:yum -y install libid ...: * elrepo: elrepo.org
Q:yum -y install libid ...: * extras: centos.crazyfrogs.org
Q:yum -y install libid ...: * rpmforge: apt.sw.be
Q:yum -y install libid ...: * updates: centos.crazyfrogs.org
Q:yum -y install libid ...:Setting up Install Process
Q:yum -y install libid ...:Package libidn-0.6.5-1.1.i386 already installed and latest version
Q:yum -y install libid ...:Nothing to do
Q:yum -y install libid ...:
Q:yum y install compa ...:Loaded plugins: fastestmirror> Command related to promiser "compat-libstdc++-33.i386" returned code defined as promise kept (0)
Q:yum -y install compa ...:Loading mirror speeds from cached hostfile
Q:yum -y install compa ...: * addons: centos.crazyfrogs.org
Q:yum -y install compa ...: * base: centos.crazyfrogs.org
Q:yum -y install compa ...: * elrepo: elrepo.org
Q:yum -y install compa ...: * extras: centos.crazyfrogs.org
Q:yum -y install compa ...: * rpmforge: apt.sw.be
Q:yum -y install compa ...: * updates: centos.crazyfrogs.org
Q:yum -y install compa ...:Setting up Install Process
Q:yum -y install compa ...:Package compat-libf2c-34-3.4.6-4.1.x86_64 already installed and latest version
Q:yum -y install compa ...:Nothing to do
Q:yum -y install compa ...:
Q:yum y install compa ...:Loaded plugins: fastestmirror> Command related to promiser "compat-libstdc++-33.i386" returned code defined as promise kept (0)
Q:yum -y install compa ...:Loading mirror speeds from cached hostfile
Q:yum -y install compa ...: * addons: centos.crazyfrogs.org
Q:yum -y install compa ...: * base: centos.crazyfrogs.org
Q:yum -y install compa ...: * elrepo: elrepo.org
Q:yum -y install compa ...: * extras: centos.crazyfrogs.org
Q:yum -y install compa ...: * rpmforge: apt.sw.be
Q:yum -y install compa ...: * updates: centos.crazyfrogs.org
Q:yum -y install compa ...:Setting up Install Process
Q:yum -y install compa ...:Package compat-libf2c-34-3.4.6-4.1.i386 already installed and latest version
Q:yum -y install compa ...:Nothing to do
Q:yum -y install compa ...:
Updated by Dennis Cabooter over 11 years ago
What I see in the CFengine logs is the following. It seems the same report is sent for all packages in the same directive. In this example only compat-libstdc++-33.i386 has a succes status.
Q:yum y install compa ...:Loaded plugins: fastestmirror Q:yum -y install compa ...:Loading mirror speeds from cached hostfile Q:yum -y install compa ...: * addons: centos.crazyfrogs.org Q:yum -y install compa ...: * base: centos.crazyfrogs.org Q:yum -y install compa ...: * elrepo: elrepo.org Q:yum -y install compa ...: * extras: centos.crazyfrogs.org Q:yum -y install compa ...: * rpmforge: apt.sw.be Q:yum -y install compa ...: * updates: centos.crazyfrogs.org Q:yum -y install compa ...:Setting up Install Process Q:yum -y install compa ...:Package compat-libstdc++-33-3.2.3-61.i386 already installed and latest version Q:yum -y install compa ...:Nothing to do Q:yum -y install compa ...: > Command related to promiser "compat-libstdc++-33.i386" returned code defined as promise kept (0) Q:yum y install compa ...:Loaded plugins: fastestmirror Q:yum -y install compa ...:Loading mirror speeds from cached hostfile Q:yum -y install compa ...: * addons: centos.crazyfrogs.org Q:yum -y install compa ...: * base: centos.crazyfrogs.org Q:yum -y install compa ...: * elrepo: elrepo.org Q:yum -y install compa ...: * extras: centos.crazyfrogs.org Q:yum -y install compa ...: * rpmforge: apt.sw.be Q:yum -y install compa ...: * updates: centos.crazyfrogs.org Q:yum -y install compa ...:Setting up Install Process Q:yum -y install compa ...:Package compat-libstdc++-33-3.2.3-61.x86_64 already installed and latest version Q:yum -y install compa ...:Nothing to do Q:yum -y install compa ...: > Command related to promiser "compat-libstdc++-33.i386" returned code defined as promise kept (0) Q:yum y install libid ...:Loaded plugins: fastestmirror Q:yum -y install libid ...:Loading mirror speeds from cached hostfile Q:yum -y install libid ...: * addons: centos.crazyfrogs.org Q:yum -y install libid ...: * base: centos.crazyfrogs.org Q:yum -y install libid ...: * elrepo: elrepo.org Q:yum -y install libid ...: * extras: centos.crazyfrogs.org Q:yum -y install libid ...: * rpmforge: apt.sw.be Q:yum -y install libid ...: * updates: centos.crazyfrogs.org Q:yum -y install libid ...:Setting up Install Process Q:yum -y install libid ...:Package libidn-0.6.5-1.1.i386 already installed and latest version Q:yum -y install libid ...:Nothing to do Q:yum -y install libid ...: > Command related to promiser "compat-libstdc++-33.i386" returned code defined as promise kept (0) Q:yum y install compa ...:Loaded plugins: fastestmirror Q:yum -y install compa ...:Loading mirror speeds from cached hostfile Q:yum -y install compa ...: * addons: centos.crazyfrogs.org Q:yum -y install compa ...: * base: centos.crazyfrogs.org Q:yum -y install compa ...: * elrepo: elrepo.org Q:yum -y install compa ...: * extras: centos.crazyfrogs.org Q:yum -y install compa ...: * rpmforge: apt.sw.be Q:yum -y install compa ...: * updates: centos.crazyfrogs.org Q:yum -y install compa ...:Setting up Install Process Q:yum -y install compa ...:Package compat-libf2c-34-3.4.6-4.1.x86_64 already installed and latest version Q:yum -y install compa ...:Nothing to do Q:yum -y install compa ...: > Command related to promiser "compat-libstdc++-33.i386" returned code defined as promise kept (0) Q:yum y install compa ...:Loaded plugins: fastestmirror Q:yum -y install compa ...:Loading mirror speeds from cached hostfile Q:yum -y install compa ...: * addons: centos.crazyfrogs.org Q:yum -y install compa ...: * base: centos.crazyfrogs.org Q:yum -y install compa ...: * elrepo: elrepo.org Q:yum -y install compa ...: * extras: centos.crazyfrogs.org Q:yum -y install compa ...: * rpmforge: apt.sw.be Q:yum -y install compa ...: * updates: centos.crazyfrogs.org Q:yum -y install compa ...:Setting up Install Process Q:yum -y install compa ...:Package compat-libf2c-34-3.4.6-4.1.i386 already installed and latest version Q:yum -y install compa ...:Nothing to do Q:yum -y install compa ...: > Command related to promiser "compat-libstdc++-33.i386" returned code defined as promise kept (0)
Updated by Matthieu CERDA over 11 years ago
- Assignee set to Matthieu CERDA
- Priority changed from N/A to 2
- Target version set to 2.3.12
Hey there Dennis, I'm on it.
Updated by Dennis Cabooter over 11 years ago
Hi Matthieu,
In order to install i386 packages on a x86_64 system
this:
package_name_convention => "$(name).$(arch)";
should be this:
package_name_convention => "$(name)";
Otherwise $(arch) will be expanded to my current arch, which is not always desireable, since I need 32 bit libraries on a 64 bit RHEL/CentOS system.
The down side of this is that you always have to specify the architecture in the package name, e.g. compat-libf2c-34.i386 and/or compat-libf2c-34.x86_64. A solution to that could be to include a dropdown with each package, where one can specify the arch, which defaults on "current architecture". How about that?
Updated by Matthieu CERDA over 11 years ago
- Status changed from New to In progress
- % Done changed from 0 to 20
OK, so this is clearly a failure in package handling.
I notice that on my testing machine (EL 6.3), there are only i686 packages:
[root@centos-6-64 tmp]# yum search libXt <useless babble ...> libXt.i686 : X.Org X11 libXt runtime library libXt.x86_64 : X.Org X11 libXt runtime library libXt-devel.i686 : X.Org X11 libXt development package libXt-devel.x86_64 : X.Org X11 libXt development package libXtst.x86_64 : X.Org X11 libXtst runtime library libXtst.i686 : X.Org X11 libXtst runtime library libXtst-devel.i686 : X.Org X11 libXtst development package libXtst-devel.x86_64 : X.Org X11 libXtst development package Name and summary matches only, use "search all" for everything.
Are those the packages you wanted to install or is my machine different ?
Updated by Matthieu CERDA over 11 years ago
Oh and you are right, I'll take a look at the reference CFEngine stdlib. We might be out of sync with it (which is bad, and thus need to be fixed ASAP). If not, well, we will fix it and report it upstream :)
Updated by Matthieu CERDA over 11 years ago
What you are proposing is a good idea of improvement in the Technique. I'm on it.
Updated by Dennis Cabooter over 11 years ago
As far as I know Rudder uses the current CFengine stdlib. I also tried to replace "package_method yum" with "package_method yum_rpm", which didn't help.
I think it would be nice to have the following arch structure per package to install:
- Choose arch - Default (current) - i386 - i486 - i586 - i686 - x86_64 - noarch
Updated by Matthieu CERDA over 11 years ago
Well, this is not trivial to fix :) Still working on it.
Updated by Dennis Cabooter over 11 years ago
I know. I tried to work on it as well. :)
Updated by Matthieu CERDA over 11 years ago
- Target version changed from 2.3.12 to 2.3.13
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.3.13 to 84
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 84 to 2.4.7
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.4.7 to 2.4.8
Updated by Nicolas PERRON over 11 years ago
- Status changed from In progress to Discussion
- Target version changed from 2.4.8 to 2.4.9
What's the news about this ticket ?
Updated by Jonathan CLARKE over 11 years ago
- Assignee changed from Matthieu CERDA to Dennis Cabooter
I think this was addressed in #3815 - at least the following change was included:
Replace
package_name_convention => "$(name).$(arch)";
With:
package_name_convention => "$(name)";
Dennis, could you test the new Technique version and confirm if it fixes this issue?
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.9 to 2.4.10
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.10 to 2.4.11
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.11 to 2.4.12
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.12 to 2.4.13
Updated by Nicolas CHARLES almost 11 years ago
I really think it has been solved; Dennis you were talking about this one this week, weren't you ?
Updated by Dennis Cabooter almost 11 years ago
Yes, it works. I can now specify:
- $packagename
- $packagename.i386
- $packagename.x86_64
Updated by Nicolas CHARLES almost 11 years ago
- Status changed from Discussion to Rejected
Ok, so i'm rejecting this bug then, as solved elsewhere
Thank you Dennis !
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 24 to Rudder
- Category changed from Techniques to Techniques