Hi Jim,
I think its a bit more serious than that, as a yum-y upgrade lists 100s
of packages with the same type of conflict....
Here is the output from "yum list packagename"
>yum list packagename
Setting up Repos
update 100% |=========================| 951 B 00:00
base 100% |=========================| 1.1 kB 00:00
addons 100% |=========================| 951 B 00:00
extras 100% |=========================| 1.1 kB 00:00
Reading repository metadata in from local files
update : ################################################## 33/33
base : ################################################## 1628/1628
extras : ################################################## 23/23
>
Output from yum -y upgrade is huge, but I give you some of it....
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..
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...
P.
Jim Perrin wrote:
>On 10/20/05, Peter Farrow <peter@xxxxxxxxxxx> wrote:
>
>
>> 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.
>>
>>
>>
>
>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
>CentOS@xxxxxxxxxx
>http://lists.centos.org/mailman/listinfo/centos
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.centos.org/pipermail/centos/attachments/20051021/1ff3cdcf/attachment.htm
