Description of problem: Attempts to install over a network or using a CD end up with "No such file or directory error". After a peek at stage2.img and netstg2.img from x86_64/Fedora/base I have a gnawing suspicion that the problem is that 'anaconda' starts with #!/usr/bin/python2.2 line but there is no 'python2.2' anywhere in sight on these images; only usr/bin/python. For all other Python files in that directory 'file' reports "a /usr/bin/python script text executable" but not for anaconda. Version-Release number of selected component (if applicable): Boot images with a time stamp "Nov 18 03:36". How reproducible: Every time.
Fixed in CVS, just working on some other changes that break trees horribly before throwing it into rawhide.
Looking at images from "Dec 14" I can see at last #!/usr/bin/python in anaconda and there are even included anaconda python libraries. There is one more catch, though. These libraries reside in usr/lib64/python2.3 while anaconda includes the following code: if os.access("/usr/lib64/python2.2/site-packages/rhpl", os.X_OK): libdir = "lib64" else: libdir = "lib" This means that 'libdir' will be set to "lib" and things will still not fly.
Closing due to inactivity. Please feel free to reopen this bug or refile this bug against the latest release Fedora Core if you feel this bug is still relevant today. Thank you