Hi; Please advise how to proceed with the following error encountered when yum install libXmu.so.6. (64 bit Intel dual core, centos 4.3). ==================== #yum install libXmu.so.6 Setting up Install Process Setting up repositories Reading repository metadata in from local files Parsing package install arguments Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package xorg-x11-libs.i386 0:6.8.2-1.EL.13.25 set to be updated --> Running transaction check --> Processing Dependency: libGL.so.1 for package: xorg-x11-libs --> Processing Dependency: libexpat.so.0 for package: xorg-x11-libs --> Processing Dependency: libz.so.1 for package: xorg-x11-libs --> Processing Dependency: libfontconfig.so.1 for package: xorg-x11-libs --> Processing Dependency: libfreetype.so.6 for package: xorg-x11-libs --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Package expat.i386 0:1.95.7-4 set to be updated ---> Package xorg-x11-Mesa-libGL.i386 0:6.8.2-1.EL.13.25 set to be updated ---> Package freetype.i386 0:2.1.9-1 set to be updated ---> Package zlib.i386 0:1.2.1.2-1.2 set to be updated ---> Package fontconfig.i386 0:2.2.3-7 set to be updated --> Running transaction check
Dependencies Resolved
============================================================================= Package Arch Version Repository Size ============================================================================= Installing: xorg-x11-libs i386 6.8.2-1.EL.13.25 base 2.7 M Installing for dependencies: expat i386 1.95.7-4 base 69 k fontconfig i386 2.2.3-7 base 116 k freetype i386 2.1.9-1 base 756 k xorg-x11-Mesa-libGL i386 6.8.2-1.EL.13.25 base 375 k zlib i386 1.2.1.2-1.2 base 44 k
Transaction Summary ============================================================================= Install 6 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 4.0 M Is this ok [y/N]: y Downloading Packages: Running Transaction Test Finished Transaction Test
Transaction Check Error: file /usr/share/man/man5/fonts-conf.5.gz from install of fontconfig-2.2.3-7 conflicts with file from package fontconfig-2.2.3-7 # ==================== Thanks nat
Transaction Check Error: file /usr/share/man/man5/fonts-conf.5.gz from install of fontconfig-2.2.3-7 conflicts with file from package fontconfig-2.2.3-7
The 64bit fontconfig is conflicting with the 32bit fontconfig. Make sure you're installing the proper arch for the lib you need, and you may have to exclude one of the fontconfig packages in your yum configs.
-- This message has been double ROT13 encoded for security. Anyone other than the intended recipient attempting to decode this message will be in violation of the DMCA
On 4/25/06, Jim Perrin jperrin@gmail.com wrote:
Transaction Check Error: file /usr/share/man/man5/fonts-conf.5.gz from install of fontconfig-2.2.3-7 conflicts with file from package fontconfig-2.2.3-7
The 64bit fontconfig is conflicting with the 32bit fontconfig. Make sure you're installing the proper arch for the lib you need, and you may have to exclude one of the fontconfig packages in your yum configs.
Two questions: 1. Doesn't yum know that its running on a 64 bit system and automatically pull the right rpm's? 2. If I need to specify 64 bit version of the aforementioned pkg (libXmu.so.6), how do I do that? Is there a naming convention for this?
Thanks; nat
Two questions:
- Doesn't yum know that its running on a 64 bit system and
automatically pull the right rpm's?
Yum knows. The problem is that you haven't told it specifically which one you want. Multiple packages provide that file. The other issue is that the 64bit centos isn't fully 64bit. There are some i386 packages in place for compatibility, and updates to them get dragged in as well. This is a reasonably common problem, and if you read/google through the list archives, you'll see several instances of it. It's not a yum issue, so much as an OS issue inherited from the upstream vendor.
- If I need to specify 64 bit version of the aforementioned pkg
(libXmu.so.6), how do I do that? Is there a naming convention for this?
I'd start off by adding/creating a file for your user and root called .rpmmacros in their respective home directories. The content of this file should be as follows:
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
Then do 'yum provides libXmu.so.6' It'll return the likely matches, showing the appropriate arch for each. Then if you want the 64bit package do 'yum install packagename.x86_64'
It should be in xorg-x11-libs.i386 or xorg-x11-libs.x86_64. You'll want to run the commands above to verify this for yourself.
-- This message has been double ROT13 encoded for security. Anyone other than the intended recipient attempting to decode this message will be found in violation of the DMCA
On 4/25/06, Jim Perrin jperrin@gmail.com wrote:
Two questions:
- Doesn't yum know that its running on a 64 bit system and
automatically pull the right rpm's?
Yum knows. The problem is that you haven't told it specifically which one you want. Multiple packages provide that file. The other issue is that the 64bit centos isn't fully 64bit. There are some i386 packages in place for compatibility, and updates to them get dragged in as well. This is a reasonably common problem, and if you read/google through the list archives, you'll see several instances of it. It's not a yum issue, so much as an OS issue inherited from the upstream vendor.
- If I need to specify 64 bit version of the aforementioned pkg
(libXmu.so.6), how do I do that? Is there a naming convention for this?
I'd start off by adding/creating a file for your user and root called .rpmmacros in their respective home directories. The content of this file should be as follows:
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
Quick question before getting into the real stuff. I put the file into /root. But do not understand what you meant to also put this file in 'user'.
Then do 'yum provides libXmu.so.6' It'll return the likely matches, showing the appropriate arch for each. Then if you want the 64bit package do 'yum install packagename.x86_64'
It should be in xorg-x11-libs.i386 or xorg-x11-libs.x86_64. You'll want to run the commands above to verify this for yourself.
The output shows that I have it installed?
First it shows: ------------------------------------- xorg-x11-libs.i386 6.8.2-1.EL.13.25 base Matched from: libXmu.so.6 ----------------------------------- Then after all the detail of pkg's added/deleted, yum style, it reports: -------------------------------------- xorg-x11-libs.x86_64 6.8.2-1.EL.13.25 base Matched from: /usr/X11R6/lib64/libXmu.so.6.2 /usr/X11R6/lib64/libXmu.so.6 libXmu.so.6()(64bit)
xorg-x11-libs.i386 6.8.2-1.EL.13.25 base Matched from: /usr/X11R6/lib/libXmu.so.6 /usr/X11R6/lib/libXmu.so.6.2 libXmu.so.6
xorg-x11-libs.x86_64 6.8.2-1.EL.13.25 base Matched from: /usr/X11R6/lib64/libXmu.so.6.2 /usr/X11R6/lib64/libXmu.so.6 libXmu.so.6()(64bit)
xorg-x11-libs.i386 6.8.2-1.EL.13.25 base Matched from: /usr/X11R6/lib/libXmu.so.6 /usr/X11R6/lib/libXmu.so.6.2 libXmu.so.6
xorg-x11-libs.x86_64 6.8.2-1.EL.13.25 installed Matched from: /usr/X11R6/lib64/libXmu.so.6 /usr/X11R6/lib64/libXmu.so.6.2 libXmu.so.6()(64bit) # -------------------------------------- Please help clarify.
Thank you much; nat
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
Quick question before getting into the real stuff. I put the file into /root. But do not understand what you meant to also put this file in 'user'.
You don't run as root all the time do you? You should have a user account that you use for most things, and if you want the same formatting options when querying rpm, you need to add this for your every-day user account also.
The output shows that I have it installed?
First it shows:
xorg-x11-libs.i386 6.8.2-1.EL.13.25 base Matched from: libXmu.so.6
If you had it installed already you'd see xorg-x11-libs.i386 6.8.2-1.EL.13.25 installed
instead, you see base, which tells you which repository the package is in.
xorg-x11-libs.x86_64 6.8.2-1.EL.13.25 base Matched from: /usr/X11R6/lib64/libXmu.so.6.2 /usr/X11R6/lib64/libXmu.so.6 libXmu.so.6()(64bit)
xorg-x11-libs.i386 6.8.2-1.EL.13.25 base Matched from: /usr/X11R6/lib/libXmu.so.6 /usr/X11R6/lib/libXmu.so.6.2 libXmu.so.6
xorg-x11-libs.x86_64 6.8.2-1.EL.13.25 base Matched from: /usr/X11R6/lib64/libXmu.so.6.2 /usr/X11R6/lib64/libXmu.so.6 libXmu.so.6()(64bit)
xorg-x11-libs.i386 6.8.2-1.EL.13.25 base Matched from: /usr/X11R6/lib/libXmu.so.6 /usr/X11R6/lib/libXmu.so.6.2 libXmu.so.6
xorg-x11-libs.x86_64 6.8.2-1.EL.13.25 installed Matched from: /usr/X11R6/lib64/libXmu.so.6 /usr/X11R6/lib64/libXmu.so.6.2 libXmu.so.6()(64bit)
#
Please help clarify.
It lists the same packages a couple times, because there are multiple files in those packages that match the query you gave it.
You need to figure out if you need the i386 version or the x86_64 version. Once you know this, then install it with yum install packagename.i386 or packagename.x86_64
Clear? ( probably not entirely... welcome to the x86 vs x86_64 version of hell.)
-- This message has been double ROT13 encoded for security. Anyone other than the intended recipient attempting to decode this message will be in violation of the DMCA
On 4/25/06, Jim Perrin jperrin@gmail.com wrote:
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
Quick question before getting into the real stuff. I put the file into /root. But do not understand what you meant to also put this file in 'user'.
You don't run as root all the time do you? You should have a user account that you use for most things, and if you want the same formatting options when querying rpm, you need to add this for your every-day user account also.
I always yum as root. Didn't realize I can use yum for 'medicore' stuff.
The output shows that I have it installed?
First it shows:
xorg-x11-libs.i386 6.8.2-1.EL.13.25 base Matched from: libXmu.so.6
If you had it installed already you'd see xorg-x11-libs.i386 6.8.2-1.EL.13.25 installed
instead, you see base, which tells you which repository the package is in.
But in the list below, the last listing, it does show 'installed'.
xorg-x11-libs.x86_64 6.8.2-1.EL.13.25 base Matched from: /usr/X11R6/lib64/libXmu.so.6.2 /usr/X11R6/lib64/libXmu.so.6 libXmu.so.6()(64bit)
xorg-x11-libs.i386 6.8.2-1.EL.13.25 base Matched from: /usr/X11R6/lib/libXmu.so.6 /usr/X11R6/lib/libXmu.so.6.2 libXmu.so.6
xorg-x11-libs.x86_64 6.8.2-1.EL.13.25 base Matched from: /usr/X11R6/lib64/libXmu.so.6.2 /usr/X11R6/lib64/libXmu.so.6 libXmu.so.6()(64bit)
xorg-x11-libs.i386 6.8.2-1.EL.13.25 base Matched from: /usr/X11R6/lib/libXmu.so.6 /usr/X11R6/lib/libXmu.so.6.2 libXmu.so.6
xorg-x11-libs.x86_64 6.8.2-1.EL.13.25 installed Matched from: /usr/X11R6/lib64/libXmu.so.6 /usr/X11R6/lib64/libXmu.so.6.2 libXmu.so.6()(64bit)
#
Please help clarify.
It lists the same packages a couple times, because there are multiple files in those packages that match the query you gave it.
You need to figure out if you need the i386 version or the x86_64 version.
Ahem. And how do I figure that out? Is there some rule of thumb? Why wouldn't I always want the 64 version?
Once you know this, then install it with yum install packagename.i386 or packagename.x86_64
Clear? ( probably not entirely... welcome to the x86 vs x86_64 version of hell.)
Gettin' there. With your help.
Thanks again. nat
But in the list below, the last listing, it does show 'installed'.
Indeed it does. I overlooked that.
xorg-x11-libs.x86_64 6.8.2-1.EL.13.25 installed Matched from: /usr/X11R6/lib64/libXmu.so.6 /usr/X11R6/lib64/libXmu.so.6.2 libXmu.so.6()(64bit)
You need to figure out if you need the i386 version or the x86_64 version.
Ahem. And how do I figure that out? Is there some rule of thumb? Why wouldn't I always want the 64 version?
Well, now we get back to why you were trying to install this lib in the first place. Since you have the 64bit package installed, and you felt the need to try to install it again anyway, you've either got poorly written source code that doesn't know enough to look for the 64bit libs, or you have a binary application, game or other such distraction that wants the 32bit lib for a reason. Not everything is 64bit compliant yet so sometimes you need the 32bit libs.
-- This message has been double ROT13 encoded for security. Anyone other than the intended recipient attempting to decode this message will be in violation of the DMCA
On 4/25/06, Jim Perrin jperrin@gmail.com wrote:
But in the list below, the last listing, it does show 'installed'.
Indeed it does. I overlooked that.
xorg-x11-libs.x86_64 6.8.2-1.EL.13.25 installed Matched from: /usr/X11R6/lib64/libXmu.so.6 /usr/X11R6/lib64/libXmu.so.6.2 libXmu.so.6()(64bit)
You need to figure out if you need the i386 version or the x86_64 version.
Ahem. And how do I figure that out? Is there some rule of thumb? Why wouldn't I always want the 64 version?
Well, now we get back to why you were trying to install this lib in the first place.
The IBM DB2 setup program would not run because it couldn't find "libXmu.so.6". I hope db2 is not poorly written! Furthermore, this is a 64 bit version from IBM!
It's kinda hard to ask them to help on this because the classical answer "RHEL is the official distro". On another *32* bit server running Fedora, I received this answer, but I finally got it to work on Fedora (4 and 5), until *they asked me* to document it as to how I got it running! AND [non-ibm] folks over on the ibm db2 list advised that with Centos I wouldn't have any problems at all. So, I get this bran new dual core 64 bit server, and I say, ok this time; clean machine, let's go Centos. <sigh> here I am.
Since you have the 64bit package installed, and you felt the need to try to install it again anyway, you've either got poorly written source code that doesn't know enough to look for the 64bit libs, or you have a binary application, game or other such distraction that wants the 32bit lib for a reason. Not everything is 64bit compliant yet so sometimes you need the 32bit libs.
Looking forward to document how I got it running on Centos<g>; nat
On Tue, 2006-04-25 at 21:50, Nat Gross wrote:
But in the list below, the last listing, it does show 'installed'.
Indeed it does. I overlooked that.
xorg-x11-libs.x86_64 6.8.2-1.EL.13.25 installed Matched from: /usr/X11R6/lib64/libXmu.so.6 /usr/X11R6/lib64/libXmu.so.6.2 libXmu.so.6()(64bit)
You need to figure out if you need the i386 version or the x86_64 version.
Ahem. And how do I figure that out? Is there some rule of thumb? Why wouldn't I always want the 64 version?
Well, now we get back to why you were trying to install this lib in the first place.
The IBM DB2 setup program would not run because it couldn't find "libXmu.so.6". I hope db2 is not poorly written! Furthermore, this is a 64 bit version from IBM!
It's kinda hard to ask them to help on this because the classical answer "RHEL is the official distro". On another *32* bit server running Fedora, I received this answer, but I finally got it to work on Fedora (4 and 5), until *they asked me* to document it as to how I got it running! AND [non-ibm] folks over on the ibm db2 list advised that with Centos I wouldn't have any problems at all. So, I get this bran new dual core 64 bit server, and I say, ok this time; clean machine, let's go Centos. <sigh> here I am.
Since you have the 64bit package installed, and you felt the need to try to install it again anyway, you've either got poorly written source code that doesn't know enough to look for the 64bit libs, or you have a binary application, game or other such distraction that wants the 32bit lib for a reason. Not everything is 64bit compliant yet so sometimes you need the 32bit libs.
Looking forward to document how I got it running on Centos<g>; nat
If it does want the 32-bit version it shouldn't hurt anything to install it with: yum install xorg-x11-libs.i386 I needed that for VMware server recently and posted here about a conflict with fontconfig from the 64-bit version. I think that's a bug but someone responded with a workaround: rpm -e --justdb --nodeps fontconfig You might also need glibc.i686.
On 4/26/06, Les Mikesell lesmikesell@gmail.com wrote:
On Tue, 2006-04-25 at 21:50, Nat Gross wrote:
<snip>
If it does want the 32-bit version it shouldn't hurt anything to install it with: yum install xorg-x11-libs.i386 I needed that for VMware server recently and posted here about a conflict with fontconfig from the 64-bit version. I think that's a bug but someone responded with a workaround: rpm -e --justdb --nodeps fontconfig
Yes! Removing fontconfig from the rpm database with the aforementioned rpm command did the trick! Thanks; nat
Les Mikesell wrote:
If it does want the 32-bit version it shouldn't hurt anything to install it with: yum install xorg-x11-libs.i386 I needed that for VMware server recently and posted here about a conflict with fontconfig from the 64-bit version. I think that's a bug but someone responded with a workaround:
rpm -e --justdb --nodeps fontconfig
which is very very wrong, and if you really care about this, dont do it. find the solution to the problem, rather than just using a hammer to break your system even more.
which in the case of the vmware-server, is to remove fontconfig.x86_64 and install fontconfig.i386 manually. The rest of your install will work then.
- KB
On Wed, 2006-04-26 at 06:53, Karanbir Singh wrote:
If it does want the 32-bit version it shouldn't hurt anything to install it with: yum install xorg-x11-libs.i386 I needed that for VMware server recently and posted here about a conflict with fontconfig from the 64-bit version. I think that's a bug but someone responded with a workaround:
rpm -e --justdb --nodeps fontconfig
which is very very wrong, and if you really care about this, dont do it. find the solution to the problem, rather than just using a hammer to break your system even more.
which in the case of the vmware-server, is to remove fontconfig.x86_64 and install fontconfig.i386 manually. The rest of your install will work then.
The solution is to not have conflicting packages in the repositories. How do we arrange that?
On Wed, Apr 26, 2006 at 07:36:54AM -0500, Les Mikesell enlightened us:
The solution is to not have conflicting packages in the repositories. How do we arrange that?
File a bug at bugzilla.redhat.com would probably be a good first step. A quick search didn't turn up anything for fontconfig at all.
Matt
Les Mikesell wrote:
On Wed, 2006-04-26 at 06:53, Karanbir Singh wrote:
If it does want the 32-bit version it shouldn't hurt anything to install it with: yum install xorg-x11-libs.i386 I needed that for VMware server recently and posted here about a conflict with fontconfig from the 64-bit version. I think that's a bug but someone responded with a workaround:
rpm -e --justdb --nodeps fontconfig
which is very very wrong, and if you really care about this, dont do it. find the solution to the problem, rather than just using a hammer to break your system even more.
which in the case of the vmware-server, is to remove fontconfig.x86_64 and install fontconfig.i386 manually. The rest of your install will work then.
The solution is to not have conflicting packages in the repositories. How do we arrange that?
:( this will need to be something from upstream... and yes i know its been a major problem for everyone who tries to multilib stuff.
one potential issue is a local fix in centos, and push patches to RH. let me work out whats involved.
On 4/26/06, Karanbir Singh mail-lists@karan.org wrote:
Les Mikesell wrote:
If it does want the 32-bit version it shouldn't hurt anything to install it with: yum install xorg-x11-libs.i386 I needed that for VMware server recently and posted here about a conflict with fontconfig from the 64-bit version. I think that's a bug but someone responded with a workaround:
rpm -e --justdb --nodeps fontconfig
which is very very wrong, and if you really care about this, dont do it. find the solution to the problem, rather than just using a hammer to break your system even more.
Now, that I did do that, how do I reverse it? nat
On Wed, 2006-04-26 at 13:49 -0400, Nat Gross wrote:
On 4/26/06, Karanbir Singh mail-lists@karan.org wrote:
Les Mikesell wrote:
If it does want the 32-bit version it shouldn't hurt anything to install it with: yum install xorg-x11-libs.i386 I needed that for VMware server recently and posted here about a conflict with fontconfig from the 64-bit version. I think that's a bug but someone responded with a workaround:
rpm -e --justdb --nodeps fontconfig
which is very very wrong, and if you really care about this, dont do it. find the solution to the problem, rather than just using a hammer to break your system even more.
Now, that I did do that, how do I reverse it?
Karanbir and I are solving this issue right now ... we should have a fix later that will work for CentOS users (I hope).
Just for the record, the upstream provider knows of the issue, which is that the file that becomes /usr/share/man/man5/fonts-conf.5.gz is not the same between the i386 build and the x86_64 build ... and they have this (private) bugzilla concerning that same problem with s390 and s390x:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=97079
Whatever they did do, they did not build their RPMS for i386 and x86_64 from the published SRPM.
As I said, hopefully we will have a patch that works later today for this issue.
Thanks, Johnny Hughes
On 4/26/06, Johnny Hughes mailing-lists@hughesjr.com wrote:
On Wed, 2006-04-26 at 13:49 -0400, Nat Gross wrote:
On 4/26/06, Karanbir Singh mail-lists@karan.org wrote:
Les Mikesell wrote:
If it does want the 32-bit version it shouldn't hurt anything to install it with: yum install xorg-x11-libs.i386 I needed that for VMware server recently and posted here about a conflict with fontconfig from the 64-bit version. I think that's a bug but someone responded with a workaround:
rpm -e --justdb --nodeps fontconfig
which is very very wrong, and if you really care about this, dont do it. find the solution to the problem, rather than just using a hammer to break your system even more.
Now, that I did do that, how do I reverse it?
Karanbir and I are solving this issue right now ... we should have a fix later that will work for CentOS users (I hope).
Just for the record, the upstream provider knows of the issue, which is that the file that becomes /usr/share/man/man5/fonts-conf.5.gz is not the same between the i386 build and the x86_64 build ... and they have this (private) bugzilla concerning that same problem with s390 and s390x:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=97079
Whatever they did do, they did not build their RPMS for i386 and x86_64 from the published SRPM.
Possibly related issue: If I do a locate so.6 using the gui frontend (search files) it reports most of the links as 'broken'. fwiw. Thanks for the coming fix. nat
updated pkgs to resolve this issue on x86_64 are now available in the updates repository.
On 4/26/06, Karanbir Singh mail-lists@karan.org wrote:
updated pkgs to resolve this issue on x86_64 are now available in the updates repository.
-- Karanbir Singh : http://www.karan.org/ : 2522219@icq
Thank you. 'yum update' pulled it in ok. nat
On Thu, 2006-04-27 at 07:02 -0400, Nat Gross wrote:
On 4/26/06, Karanbir Singh mail-lists@karan.org wrote:
updated pkgs to resolve this issue on x86_64 are now available in the updates repository.
-- Karanbir Singh : http://www.karan.org/ : 2522219@icq
Thank you. 'yum update' pulled it in ok. nat
OK ... you should have both fontconfigs installed ... the i386 version and the x86_64 version. This command should show 2 files:
rpm -q fontconfig
If not, install them both with:
yum install fontconfig.i386 fontconfig.x86_64
On 4/27/06, Johnny Hughes mailing-lists@hughesjr.com wrote:
On Thu, 2006-04-27 at 07:02 -0400, Nat Gross wrote:
On 4/26/06, Karanbir Singh mail-lists@karan.org wrote:
updated pkgs to resolve this issue on x86_64 are now available in the updates repository.
-- Karanbir Singh : http://www.karan.org/ : 2522219@icq
Thank you. 'yum update' pulled it in ok. nat
OK ... you should have both fontconfigs installed ... the i386 version and the x86_64 version. This command should show 2 files:
rpm -q fontconfig
If not, install them both with:
yum install fontconfig.i386 fontconfig.x86_64
Thanks for the pointer. Indeed I only had one of them installed, now it shows both. -nat
-
Jim Perrin -
Johnny Hughes -
Karanbir Singh -
Les Mikesell -
Matt Hyclak -
Nat Gross