Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 77126 - Installer hangs while reading package information
Summary: Installer hangs while reading package information
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-kickstart
Version: 8.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-11-01 15:07 UTC by Ruan Viljoen
Modified: 2007-04-18 16:48 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-11-05 20:41:04 UTC


Attachments (Terms of Use)
Comment (75.99 KB, text/plain)
2002-11-01 15:07 UTC, Ruan Viljoen
no flags Details

Description Ruan Viljoen 2002-11-01 15:07:44 UTC
Created attachment 915134 [details]
Comment

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).

Comment 1 Michael Fulbright 2002-11-01 16:21:04 UTC
It appears the custom comps file you have created may have problems.

If you attempt to install from an unmodified tree does it work?

Comment 2 Ruan Viljoen 2002-11-04 07:26:33 UTC
We have not tweaked the installation at all, except for building the kickstart 
file.  If I install from that same ftp location, without the ks file, the 
install works fine.The comps file has not changed at all.

Comment 3 Michael Fulbright 2002-11-05 20:40:55 UTC
Ok I understand - remove 'Minimal' from the end of the kickstart file.

This appears to be a bug with the ks generation program.

Comment 4 Brent Fox 2002-11-06 19:46:47 UTC
Yep.  Fix committed to cvs.  I removed the "Minimal" and "Everything" choices
since they aren't in comps.xml anymore.  Should be fixed in
redhat-config-kickstart-2.3.3-5.  Thanks for your report.


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