Bug 72899 - Upgrade from 7.2 to 7.3 fails when reading package info
Summary: Upgrade from 7.2 to 7.3 fails when reading package info
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-08-28 20:52 UTC by Bob T.
Modified: 2007-04-18 16:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-10-03 21:19:15 UTC
Embargoed:


Attachments (Terms of Use)
Anaconda error dump (24.00 KB, text/plain)
2002-08-28 20:58 UTC, Bob T.
no flags Details
Anaconda error dump (24.25 KB, text/plain)
2002-08-28 21:05 UTC, Bob T.
no flags Details
Anaconda log . (55.32 KB, text/plain)
2002-09-05 01:23 UTC, Bob T.
no flags Details

Description Bob T. 2002-08-28 20:52:18 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (X11; U; Linux 2.4.18-10 i586)

Description of problem:
Python crashes with trace and
RuntimeError: /bin/sh can not be run


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


How reproducible:
Always

Steps to Reproduce:
1. try to upgrade from 7.2 to 7.3
2. after boot-loader configuration, "reading package info" window
opens
3. 
	

Actual Results:  Error window opens with Python traceback and debugging info
(attached).

Expected Results:  upgrade

Additional info:

Comment 1 Bob T. 2002-08-28 20:58:06 UTC
Created attachment 73604 [details]
Anaconda error dump

Comment 2 Bob T. 2002-08-28 21:05:06 UTC
Created attachment 73605 [details]
Anaconda error dump

Comment 3 Michael Fulbright 2002-08-29 16:20:24 UTC
The error log you attached is truncated - please attach the entire file.

Comment 4 Bob T. 2002-09-05 01:23:48 UTC
Created attachment 74964 [details]
Anaconda log .

Comment 5 Bob T. 2002-09-05 01:29:21 UTC
Sorry for the truncated log and the delay. The original floppy had bad sectors,
and the computer had gone off to college with my son.

Comment 6 Jeremy Katz 2002-10-02 21:57:41 UTC
What does `ls -l /bin/sh` give on your system?

Comment 7 Bob T. 2002-10-03 01:38:12 UTC
$ ls -l /bin/sh
   0 lrwxrwxrwx    1 root     root    9 May  5 03:51 /bin/sh -> /bin/bash*

Comment 8 Jeremy Katz 2002-10-03 01:57:38 UTC
What is the output of the following commands?

rpm -qf /bin/sh
rpm -V bash


/bin/sh should be a symbolic link to just bash instead of /bin/bash so I'm just
curious as to how it got to its current state.  We have code in Red Hat Linux
8.0 to make sure that this symlink is correct before going into the upgrade process.

Comment 9 Bob T. 2002-10-03 21:19:08 UTC
bash-2.05-8 is installed.  Unfortunately, bash was re-installed before rpm -V
was run and no one knows how the sym link could have become /bin/bash.

Comment 10 Jeremy Katz 2002-10-05 13:43:28 UTC
Hmm... okay -- well, if you fix it, then your upgrade should work.  As I said,
we detect this case and handle it better in Red Hat Linux 8.0

Comment 11 Michael Fulbright 2002-12-20 17:38:25 UTC
Time tracking values updated


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