From: Alfred von Campe alf...@von-campe.com
I have been using 32-bit CentOS since the 4.X days without a real need for
64-bit, but in preparation for CentOS 7, I have installed 64-bit CentOS 6 on
a
test system to qualify all our builds. However, in order to build some of
our
current
On Feb 25, 2014, at 6:13, John Doe jd...@yahoo.com wrote:
Maybe try 'protected_multilib' in yum.conf (see man).
Thanks for the hint. Upon closer inspection, the issue was with glib from
rpmforge, so doing a yum update --disablerepo=rpmforge\* makes it work.
Alfred
From: Alfred von Campe alf...@von-campe.com
Thanks for the hint. Upon closer inspection, the issue was with glib from
rpmforge, so doing a yum update --disablerepo=rpmforge\* makes
it work.
You Should set up repos priorities...
JD
___
CentOS
I have been using 32-bit CentOS since the 4.X days without a real need for
64-bit, but in preparation for CentOS 7, I have installed 64-bit CentOS 6 on a
test system to qualify all our builds. However, in order to build some of our
current 32-bit applications, I had to install some i686
On 2/24/2014 3:18 PM, Alfred von Campe wrote:
However, in order to build some of our current 32-bit applications, I had to
install some i686 packages, including glib.
how did you do these installs? I've never had trouble doing it via
yum, like: yum install glibc.i686
but then, I've
On Feb 24, 2014, at 18:59, John R Pierce pie...@hogranch.com wrote:
how did you do these installs? I've never had trouble doing it via
yum, like: yum install glibc.i686
That's exactly what I did, and it worked fine (I can compile our 32-bit apps),
but I get the error when I try to do
What is the best way to proceed with the yum update so that all (64-bit
and 32-bit) packages are updated?
I usually check the dependency error and will install the missing 32bit
package alone ( one time task ), then will try yum update . I think,
rpm/repo compose file decides the dependency
7 matches
Mail list logo
