Bug 224124 - /usr/lib/anaconda-runtime/pkgorder error
/usr/lib/anaconda-runtime/pkgorder error
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-24 04:10 EST by Zhang Yanmin
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-01-26 10:54:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Zhang Yanmin 2007-01-24 04:10:30 EST
Description of problem:
/usr/lib/anaconda-runtime/pkgorder reported errors

Version-Release number of selected component (if applicable):
anaconda-11.2.0.13-1.ia64.rpm

How reproducible:
Everytime

Steps to Reproduce:
1. Run #/usr/lib/anaconda-runtime/pkgorder /root/os ia64 Fedora
2. It failed
3.
  
Actual results:
Traceback (most recent call last):
  File "/usr/lib/anaconda-runtime/pkgorder", line 33, in <module>
    from yuminstall import YumSorter
  File "/usr/lib/anaconda/yuminstall.py", line 34, in <module>
    from backend import AnacondaBackend
  File "/usr/lib/anaconda/backend.py", line 23, in <module>
    import kickstart
  File "/usr/lib/anaconda/kickstart.py", line 17, in <module>
    from installclass import BaseInstallClass, availableClasses, getBaseInstallClass
  File "/usr/lib/anaconda/installclass.py", line 22, in <module>
    from instdata import InstallData
  File "/usr/lib/anaconda/instdata.py", line 25, in <module>
    import bootloader
  File "/usr/lib/anaconda/bootloader.py", line 31, in <module>
    import booty
ImportError: No module named booty


Expected results:
No such error.

Additional info:
Comment 1 Zhang Yanmin 2007-01-26 02:24:10 EST
anaconda-11.2.0.15-1 has no such issue. So the report could be closed now.

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