yum and up2date unexpectedly quit (librpmio issue, I think)
Jon
jon at plainculture.com
Sun Mar 14 17:09:46 UTC 2004
Sam Varshavchik wrote:
> Jon writes:
>
>>>
>> Well, I'm not sure why the segmentation fault (the dumb thing...),
>> but this is how it comes out:
>>
>> [jon at localhost jon]$ rpm -q up2date yum rpm rpm-devel
>> up2date-4.3.11-2.1.1
>> yum-2.0.5.20040310-1
>> rpm-4.3-0.20
>> Segmentation fault
>> [jon at localhost jon]$
>>
>> I haven't tried upgrading to glibc manually, so I'm going to try
>> that. I often try to avoid updating glibc for as much as I can...
>
>
> If rpm itself is segfaulting here, then I would suspect a corrupt rpm
> database.
>
> Go to /var/lib/rpm and remove all the __db.* crap. If that still
> doesn't fix it try rpm --rebuilddb. And if that doesn't work, you're
> screwed.
>
>
Never mind, it was screwed because of glibc (I believe). After getting
it updated, it comes out without the seg fault.
[jon at localhost jon]$ sudo rpm -q up2date yum rpm rpm-devel
up2date-4.3.11-2.1.1
yum-2.0.5.20040310-1
rpm-4.3-0.20
rpm-devel-4.3-0.9.1
Thanks anyway.
--
Jon MacG.
jon.plainculture.com
More information about the fedora-test-list
mailing list