Bug 52311

Summary: rpm 4.0.2 seg faults when installing Kernel 2.2.19 after installing db3
Product: [Retired] Red Hat Linux Reporter: Need Real Name <curtis>
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-08-22 17:43:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
This is the core dump that occurs when the problem occurs none

Description Need Real Name 2001-08-22 17:40:27 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2 i586)

Description of problem:
rpm -ivh kernel-2.2.19-6.2.7.i386.rpm
error: cannot open Depends index using db1 - Invalid arugment (22)
Segmentation fault (core dumped)

All current updates had been applied and I was attempting to upgrade the
kernel.  I had already upgraded kernel-pcmcia-cs kernel-docs kernel-source
kernel-headers and kernel-doc.  


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install all current bugfixes listed in the errata (downloaded from
sunsite.unc.edu)
2. then after upgrading ancillary rpms the install of the kernel fails. 
The command entered is rpm -ivh kernel-2.2.19-6.2.7.i386.rpm
3.  
	

Actual Results:  error: cannot open Depends index using db1 - Invalid
argument (22)
Segmentation fault (core dumped)

Expected Results:  The kernel should have installed.  At that point I would
have gone on to make the RAM disk images.  	

Additional info:

This is the final step in the upgrade.  It'll probably run OK, but  This
unit is my main DNS server.  It really needs to be stable.  Up until now it
has been.  It has been up for 363 days.  I hope it continues to run in its
current state.
Comment 1 Need Real Name 2001-08-22 17:43:44 UTC 
Created attachment 28974 [details]
This is the core dump that occurs when the problem occurs
Comment 2 Jeff Johnson 2001-08-22 18:08:35 UTC 
Hmmm, you've neglected to do "rpm --rebuilddb" to convert
from db1 -> db3 format. Try that now ...

If that fails, the best solution is to upgrade to rpm-4.0.3,
which handles db errors far better than rpm-4.0.2. You
will probably need to do that using rpm2cpio

Get 6.2 packages from ftp://ftp.rpm.org/pub/rpm/test-4.0.3, there
are 5 packages all with 6x in the release. Then do
	mkdir /var/tmp/xxx
	cd /var/tmp/xxx
	rpm2cpio rpm-4.0.3-0.57.6x.i386.rpm | cpio -dim
	find . -type d -exec chmod 755 {} \;
	tar cf - . | (cd /; tar xvf -)
and then do a "rpm --rebuilddb".

If that works, either reinstall rpm-4.0.2 packages, or
install rpm-4.0.3 packages as well as versions of gnorpm, kpackage etc
that are linked with rpm-4.0.3 libraries.
Comment 3 Need Real Name 2001-08-22 19:05:11 UTC 
Thanks.  That fixed it.

-Curtis