Description of problem: Version-Release number of selected component (if applicable): anaconda-17.2 How reproducible: Steps to Reproduce: 1. create install DVD from rawhide for Fedora 17 (Tues.Dec.6) 2. boot for install 3. Actual results: early abort with: file /usr/bin/anaconda line 606 in <module> from pyanaconda import kickstart file kickstart.py line 32 from errors import * ImportError: no module named errors Expected results: successful entry to installer Additional info:
Created attachment 541632 [details] /tmp/anaconda.log
Created attachment 541633 [details] /tmp/program.log
Created attachment 541634 [details] /tmp/syslog
Some of the errors from errors.py removed in commit 56013c987fb563076708051a7480f9cb7d8b9c96 are still used.
Ping? Nine days ago (12/13/2011) bugzilla mail says Status is POST, which according to Help means that a proposed change has been posted to anaconda-devel-list. I cannot find such a message, and the current package still is anaconda-17.2, and the ImportError persists after using new lorax-17.1-1.fc17.x86_64 to build an install DVD for rawhide for Fedora 17.
Patch was pushed to master branch: commit 58d7cc4e4f6a16 We haven't done a new build. Most (all) of our efforts are on another branch at this time. Feel free to clone git and make yourself an updates image in the meantime. Will be fixed in anaconda-17.3.
*** Bug 784115 has been marked as a duplicate of this bug. ***
could you guys please fire through a build to fix this today or tomorrow? we have a RATS test scheduled for thursday and we'd like a usable build of anaconda or else we can't do any meaningful testing. First Alpha TC is scheduled for next week. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers