On Sep 15, 2011, at 7:18 AM, sebastiano@xxxxxxxxxxxxx wrote:
> On Thu, 15 Sep 2011 05:57:02 -0700, Craig White wrote:
>> sounds like someone did some manual mucking in /etc/yum.repos.d
>>
>> You probably want to start disabling some of the configured repo's
>> in /etc/yum.repos.d... 'enabled = 0' - I'd probably start by making
>> sure
>> that all non-CentOS repo's were disabled though it does seem like you
>> don't get very far through the repo list.
>>
>> At the point where you stop getting the segfault, you will be able to
>> identify which repo has a configuration issue.
>
> That was a very good idea, I have tried it:
>
> - if I disable all repositories I get no errors but no updates (which
> is normal)
> - if I enable [base] only I get the segmentation fault
> - if I enable [updates] only I get the following output, which confirms
> that yum at least partially works: the missing package is in the [base]
> repository, which is the one that gives the error
>
> [root@picard yum.repos.d]# yum update
> Loaded plugins: downloadonly, fastestmirror, priorities
> Determining fastest mirrors
> * updates: mirror.opendoc.net
> updates
> | 1.9 kB 00:00
> updates/primary_db
> | 134 kB 00:00
> Excluding Packages in global exclude list
> Finished
> Setting up Update Process
> Resolving Dependencies
> --> Running transaction check
<<<snip>>>
> You could try using --skip-broken to work around the problem
> You could try running: package-cleanup --problems
> package-cleanup --dupes
> rpm -Va --nofiles --nodigest
----
might be hard to run package-cleanup without having base enabled but I would certainly recommend that you run 'rpm -Va [--nofiles --nodigest]' to identify the broken dependencies - apparently something that the base repository really believes should be there no matter what.
Craig
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
