Bug 76464

Summary:	rpm does not return from Upgrade command
Product:	[Retired] Red Hat Linux	Reporter:	Florin Andrei <florin>
Component:	rpm	Assignee:	Jeff Johnson <jbj>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0
Target Milestone:	---
Target Release:	---
Hardware:	athlon
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-10-22 02:57:10 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:

Description Florin Andrei 2002-10-22 02:39:43 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
get transcode-0.6.2.20021021 tarball from here:
http://www.theorie.physik.uni-goettingen.de/~ostreich/transcode/pre/
Rebuild it:
rpmbuild -ta --rebuild --target=athlon transcode....
Then install the binary:
rpm -Uvh transcode....
The last command does not return the prompt in xterm. I tried to kill the rpm
process, but it does not respond; i didn't tried a -9 yet.

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


How reproducible:
Didn't try

Steps to Reproduce:
1.rebuild transcode-0.6.2.20021021
2.install (-U) the binary
3.
	

Actual Results:  rpm command is frozen

Expected Results:  rpm should upgrade the package

Additional info:

Comment 1 Florin Andrei 2002-10-22 02:57:02 UTC

Ok, i "kill -9"'ed rpm, run a "rpm -qa | grep transcode", and sure thing, there
were two versions installed.
I removed dvd::rip first (it depends on transcode), then did a "rpm -ev
--allmatches transcode".
Then i attempted again to install my newly built package. It worked. I
reinstalled dvd::rip afterwards... Nothing suspicious so far.
But i wonder if my RPM database is still healthy. :-(

Comment 2 Jeff Johnson 2002-10-23 14:58:57 UTC

Doing --rebuilddb with rpm-4.1 guarantees (by checking signatures
and digests of headers, and rebuilding all other indices)
a "healthy" database, for some pretty meaningful definition
of "healthy".