<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi Jim,<br>
<br>
I think its a bit more serious than that, as a yum-y upgrade lists 100s
of packages with the same type of conflict....<br>
<br>
Here is the output from "yum list packagename"<br>
<font face="Courier New, Courier, monospace">>yum list packagename<br>
Setting up Repos<br>
update 100% |=========================| 951 B
00:00<br>
base 100% |=========================| 1.1 kB
00:00<br>
addons 100% |=========================| 951 B
00:00<br>
extras 100% |=========================| 1.1 kB
00:00<br>
Reading repository metadata in from local files<br>
update : ################################################## 33/33<br>
base : ################################################## 1628/1628<br>
extras : ################################################## 23/23<br>
</font>><br>
<br>
Output from yum -y upgrade is huge, but I give you some of it....<br>
<br>
The history of this is that the first yum -y upgrade went ok, (296
packages) but I ctrl-c'ed two by mistake as it was downloading them,
yum carried on and installed the rest, but I thought I would yum again
to get the two I missed and this problem cropped up..<br>
<br>
Now it wants to update them all again and list a conflict for each...
the error output for yum was not captured in the file I redirected it
to, but essentially its the same as the one for mysql I showed you
earlier but for every package it seems...<br>
<br>
<br>
P.<br>
<br>
<br>
<br>
<br>
<br>
Jim Perrin wrote:<br>
<blockquote type="cite"
cite="mid302ce8b50510201731h7290311ewffc61b38111d20eb@mail.gmail.com">
<pre wrap="">On 10/20/05, Peter Farrow <a class="moz-txt-link-rfc2396E" href="mailto:peter@farrows.org"><peter@farrows.org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Hi Jim,
yes I did add the line you suggested straight away and indeed shows the
multi-arch packages as you describe...
however the yum snapshot was consitent with and without the macro
definition for rpm, and still doesn't work.
</pre>
</blockquote>
<pre wrap=""><!---->
Okay, so if it's listing both versions of the same package, then the
next step is to check yum to see what's available, WITH the script in
.rpmmacros. 'yum list packagename' should show you the packages
available. My suspicion is that there's an upgrade for one, but not
the other, which would lead to your conflict. If this is indeed the
case, please paste the versions and the yum output here (again, with
the script in .rpmmacros) so that we can see where the problem is. It
may be something on the repository end that was overlooked, or it
could be something as simple as removing one of the packages. To be
safe, I'd like to see what's there before I say to just go ahead and
uninstall one of them.
--
Jim Perrin
System Administrator - UIT
Ft Gordon & US Army Signal Center
_______________________________________________
CentOS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CentOS@centos.org">CentOS@centos.org</a>
<a class="moz-txt-link-freetext" href="http://lists.centos.org/mailman/listinfo/centos">http://lists.centos.org/mailman/listinfo/centos</a>
</pre>
</blockquote>
</body>
</html>