Bug 36693 - installation aborts during
installation aborts during
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.1
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Brent Fox
Brock Organ
http://thales.memphis.edu/~mw/anacdum...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-04-19 17:54 EDT by mw
Modified: 2007-04-18 12:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-05-14 16:25:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description mw 2001-04-19 17:54:41 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2 i686)


Both trying to install from a local harddrive or via ftp, I get the 7.0 ->
7.1 upgrade 
abort during "finding packages to be upgraded".  The URL contains the
floppy dum anaconda offered.  I'd like to add that now rpm dumps core
whenever I try to install *any* package.

Reproducible: Always
Steps to Reproduce:
1. insert boot.img floppy
2. press RET at boot:.
3. after selecting "Upgrade existing install", just wait a bit...
	

Actual Results:  crash

Expected Results:  installation proceed normally

I'd like to add that now rpm dumps core whenever I try to install *any*
package:

# rpm -Uvh mouseconfig-4.21-1.i386.rpm 
Segmentation fault (core dumped)

# rpm -Uvh pam-*                       
Segmentation fault (core dumped)

This is with the old (7.0's ?) rpm:

# rpm -q rpm
rpm-4.0-4
Comment 1 Brent Fox 2001-04-19 23:20:56 EDT
Jeff, is this the same problem with corrupted RPM databases that we saw a few
months ago?
Comment 2 Brent Fox 2001-05-03 14:59:43 EDT
Can you attach the complete debug message?
Comment 3 Brent Fox 2001-05-14 16:25:17 EDT
Closing due to inactivity.  Please reopen if you have more information.


Note You need to log in before you can comment on or make changes to this bug.