Bug 174034 - anaconda crashes when file not found on mirror
Summary: anaconda crashes when file not found on mirror
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 5
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
: 174035 (view as bug list)
Depends On:
Blocks: FC5Blocker
TreeView+ depends on / blocked
Reported: 2005-11-23 23:24 UTC by Mary Ellen Foster
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-01-21 03:54:05 UTC
Type: ---

Attachments (Terms of Use)
anacdump.txt generated by anaconda (744.15 KB, text/plain)
2005-11-23 23:30 UTC, Mary Ellen Foster
no flags Details

Description Mary Ellen Foster 2005-11-23 23:24:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.0 (like Gecko) Kubuntu 6.04 Dapper

Description of problem:
This is probably not unexpected ... I just tried an HTTP install of FC5T1 from 
mirrorservice.org, and it seems to have an incomplete set of RPMs. So I went 
through the whole configuration process, and then when it started to download 
things I it didn't find libXext and exited. 
I can't see that this can be much better ... but at least it should fail in a 
less scary way. I'll attach the "anacdump.txt" file that I copied to my other 
laptop (cool feature!). 

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

How reproducible:
Didn't try

Steps to Reproduce:
1. Try to do a network install of FC5T1 using an incompletely synchronised 

Additional info:

Comment 1 Mary Ellen Foster 2005-11-23 23:27:44 UTC
*** Bug 174035 has been marked as a duplicate of this bug. ***

Comment 2 Mary Ellen Foster 2005-11-23 23:30:46 UTC
Created attachment 121422 [details]
anacdump.txt generated by anaconda

Comment 3 Jeremy Katz 2005-11-25 03:07:00 UTC
Yeah, handling of package download errors is currently very poor.  On the list
to be sure is fixed before release

Comment 4 Jeremy Katz 2006-01-21 03:54:05 UTC
This should be handled properly now

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