Hi Everyone,
I've got a system running CentOS 4 x86_64 and have some i386 packages (e.g. Firefox) installed, too. I knew when I started out that this wasn't ideal, but worked nonetheless. And, so far, it has. I'm (and my client) are happy!
A couple of days ago I updated the server from U2 to U3 (it's not a public system, and runs some critical software...U3 couldn't go in right away). Everything appeared to be going well until it came time to install the updates, when yum barfed:
Transaction Check Error: file /usr/share/man/man1/asn1parse.1ssl.gz from install of openssl-0.9.7a-43.8 conflicts with file from package openssl-0.9.7a-43.8 file /usr/share/man/man1/nseq.1ssl.gz from install of openssl-0.9.7a-43.8 conflicts with file from package openssl-0.9.7a-43.8 file /usr/share/man/man1/s_client.1ssl.gz from install of openssl-0.9.7a-43.8 conflicts with file from package openssl-0.9.7a-43.8 file /usr/share/man/man1/s_server.1ssl.gz from install of openssl-0.9.7a-43.8 conflicts with file from package openssl-0.9.7a-43.8 file /usr/share/man/man1/sslpasswd.1ssl.gz from install of openssl-0.9.7a-43.8 conflicts with file from package openssl-0.9.7a-43.8
Looks like the x86_64 and i386 openssl packages install their man pages to the same location. I was able to complete the update after excluding openssl.
I'm not sure how other packages handle this, but it looks like a bug. However, I found a mail list thread where Karanbir or Johnny (not sure which one) indicated that this had been fixed. Well, the update is not going in for me, so something is fubar.
Anyone else dealing with this? Is there a workaround or fix I'm not aware of? I'd appreciate any pointers.
Thanks,
Ranbir
Kanwar Ranbir Sandhu wrote:
Transaction Check Error: file /usr/share/man/man1/asn1parse.1ssl.gz from install of openssl-0.9.7a-43.8 conflicts with file from package openssl-0.9.7a-43.8 file /usr/share/man/man1/nseq.1ssl.gz from install of openssl-0.9.7a-43.8 conflicts with file from package openssl-0.9.7a-43.8 file /usr/share/man/man1/s_client.1ssl.gz from install of openssl-0.9.7a-43.8 conflicts with file from package openssl-0.9.7a-43.8 file /usr/share/man/man1/s_server.1ssl.gz from install of openssl-0.9.7a-43.8 conflicts with file from package openssl-0.9.7a-43.8 file /usr/share/man/man1/sslpasswd.1ssl.gz from install of openssl-0.9.7a-43.8 conflicts with file from package openssl-0.9.7a-43.8
Looks like the x86_64 and i386 openssl packages install their man pages to the same location. I was able to complete the update after excluding openssl.
this is not a problem, lots of packages do this.
I'm not sure how other packages handle this, but it looks like a bug.
the bug would be something to do with the way that package ( either the x86_64 or the i386 one ) was built, or it could also be you had i386 repo's enabled on the machine, and ran updates / installs against that ). We've had another person complain about this and open a bug, but neither me nor Johnny were able to reproduce this issue, so cant really start looking for a fix.....
if you can, add some reproduceability instructions and add to bug #1356 at http://bugs.centos.org/ that would help sort this issue out.
On Tue, 2006-13-06 at 00:04 +0100, Karanbir Singh wrote:
the bug would be something to do with the way that package ( either the x86_64 or the i386 one ) was built, or it could also be you had i386 repo's enabled on the machine, and ran updates / installs against that ).
I have a i386 repo configured for CentOS-Base (CentOS-Base-i386.repo), but the only package enabled in it is Firefox. I also have kbsingh-CentOS-Extras, kbsingh-CentOS-Misc, and rpmforge repos, but they are all disabled. So, yum updates run against the x86_64 CentOS-Base repo, except for Firefox.
if you can, add some reproduceability instructions and add to bug #1356 at http://bugs.centos.org/ that would help sort this issue out.
Okay, will do.
Regards,
Ranbir
On Tue, 2006-13-06 at 12:41 -0400, Kanwar Ranbir Sandhu wrote:
I have a i386 repo configured for CentOS-Base (CentOS-Base-i386.repo), but the only package enabled in it is Firefox. I also have kbsingh-CentOS-Extras, kbsingh-CentOS-Misc, and rpmforge repos, but they are all disabled. So, yum updates run against the x86_64 CentOS-Base repo, except for Firefox.
Now that I think about it, that's probably the problem. Installing firefox.i386 would have pulled in openssl.i386, etc. Don't know how to get around this since I haven't seen any 64bit versions of the plugins currently in use.
Anyone else running openssl.i386 and openssl.x86_64 on a x86_64 machine?
Regards,
Ranbir
Kanwar Ranbir Sandhu wrote:
Anyone else running openssl.i386 and openssl.x86_64 on a x86_64 machine?
We are. Had a hassle getting all the i386 and x86_64 stuff to kickstart and work, until we kickstarted with the "Compatibility Arch Support" install group. No prob after that, but I'm not sure whether you can just install that group on an installed system and fix the issue. -Alan
Kanwar Ranbir Sandhu wrote:
On Tue, 2006-13-06 at 00:04 +0100, Karanbir Singh wrote:
I have a i386 repo configured for CentOS-Base (CentOS-Base-i386.repo), but the only package enabled in it is Firefox. I also have kbsingh-CentOS-Extras, kbsingh-CentOS-Misc, and rpmforge repos, but they are all disabled. So, yum updates run against the x86_64 CentOS-Base repo, except for Firefox.
I had a similar problem, I needed the i686 version of openssl on my shiny, new 64-bit version and it just would not go. What I ended up doing was running "yum install openssl.i686" and noting the dependencies when it failed, then reran yum to install the dependencies. Finally I downloaded the openssl RPM for i686 and did an "rpm -ivh --excludedocs openssl*.i686.rpm" to get it all installed. Since all of the conflicts were in the manpages, this worked out nicely. Perhaps there will be problems later, but the install was clean and it seems to work just fine. Now if I can just figure out why nxserver won't work on that system...
Just a thought!
Jay Leafey wrote:
I had a similar problem, I needed the i686 version of openssl on my shiny, new 64-bit version and it just would not go. What I ended up doing was running "yum install openssl.i686" and noting the dependencies when it failed, then reran yum to install the dependencies. Finally I downloaded the openssl RPM for i686 and did an "rpm -ivh --excludedocs openssl*.i686.rpm" to get it all installed. Since all of the conflicts were in the manpages, this worked out nicely. Perhaps there will be problems later, but the install was clean and it seems to work just fine. Now if I can just figure out why nxserver won't work on that system...
what are the chances that you could perhaps email me offlist the yum.log and the output of rpm --qa --last, from that machine ? ( for rpm, make sure its reporting the .arch as well ).
Kanwar, would you be able to do this as well ? since you are presently having this issue, lets see if we can work through this.
- KB
On Thu, 2006-15-06 at 10:00 +0100, Karanbir Singh wrote:
what are the chances that you could perhaps email me offlist the yum.log and the output of rpm --qa --last, from that machine ? ( for rpm, make sure its reporting the .arch as well ).
Kanwar, would you be able to do this as well ? since you are presently having this issue, lets see if we can work through this.
Did the logs, etc., I sent you contain any pertinent info?
I'm going to try out Jay's suggestion soon, unless you have something better in mind. If you do, let me know. Otherwise, I'll report here if Jay's solution works for me.
Regards,
Ranbir
-
Alan Sparks -
Jay Leafey -
Kanwar Ranbir Sandhu -
Karanbir Singh