Bug 160660
| Summary: | Installer, text mode: ImportError: No module named email.Utils | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Igor Bukanov <igor> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | CC: | ermeyers, kevin, ltcgcw, oliva, ryan, xtremeq_g |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-10-11 18:14:27 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Igor Bukanov
2005-06-16 14:04:25 UTC
Same here: I tried to upgrade FC3 to FC4 using a HD install started from GRUB,
using the CD ISOs. I get:
...
File "/usr/lib/python2.4/urllib2.py", line 1131, in open_local_file
import email.Utils
ImportError: No module named email.Utils
Anything I can do about that, other than waiting for FC5 or trying my luck with
apt or yum?
Here's a workaround that appears to work for me (but I didn't get beyond the disk space check; I need to clean up before retrying the upgrade). WARNING: This will work for UPGRADES (from sufficiently recent RHL/Fedora releases) ONLY! mkdir /mnt/sysimage/tmp/fc4installpython2.4 cp -r /usr/lib/python2.4/* /mnt/sysimage/tmp/fc4installpython2.4 nano /mnt/sysimage/tmp/fc4installpython2.4/urllib2.py * remove "import email.Utils" * change "modified = email.Utils.formatdate(stats.st_mtime, usegmt=True)" to "modified = '2000-01-01'" (in order to get rid of the use of email.Utils, which is not available in Anaconda) /mnt/sysimage/bin/mount -- bind /mnt/sysimage/tmp/fc4installpython2.4 /usr/lib/python2.4/ This wierd copying and rebinding hack is needed because the file system is mounted read-only from the ISO. Also make sure you use /mnt/sysimage/bin/mount, because the Busybox builtin mount doesn't understand the --bind option. Someone at RH will have to rebuild a working ISO for a real fix. I should add that all these commands need to be entered on the console you get by pressing Alt+F2, when Anaconda is on the window asking you how to proceed with the GRUB configuration. (The window before is too early, because you need /mnt/sysimage, the one afterwards is too late, because it is already the backtrace.) I can confirm that my workaround allowed me to upgrade FC3 to FC4, but I needed to run the installer 3 times to get the upgrade to complete (it spontaneously rebooted during the installation the first 2 times). But that is probably a separate issue, so I opened another bug report. See bug 160944 for details. I upgraded my installation using network install from public ftp server. It worked in the text mode without any problems. So the bug shows itself only when using iso images stored on the harddrive. If I would know that I would not even bother to get the DVD image via torrent. *** Bug 161178 has been marked as a duplicate of this bug. *** I can confirm that Kevin Kofler's workaround works also for reinstalls with slight modifications. I got the Python trace screen after the Root Password screen. I istalled from hard drive without any other boot media, using kernel and initrd from the isolinux on FC4-i386-DVD.iso. Since I didn't get sysimage, I used "/tmp/fc4installpython2.4" folder instead. I also had to use vi instead of nano. To make the --bind trick I mounted my previous FC2 partition and used FC2's mount. Anaconda didn't crash any more but I got an (unrelated) reboot at the first boot. Too bad FC4 is so buggy. It seems like every time I make a fresh install it gets harder because of new bugs. Fixed in CVS. *** Bug 170683 has been marked as a duplicate of this bug. *** *** Bug 170576 has been marked as a duplicate of this bug. *** *** Bug 174448 has been marked as a duplicate of this bug. *** *** Bug 180760 has been marked as a duplicate of this bug. *** |