After installation, the saved anaconda-ks.cfg contained a bunch of
extra packages to
be removed such as:
-iprutils
-yaboot
-ppc64-utils
-elilo
-s390utils
-vixie-cron
-bc
-lsof
-ksh
Yeah it's pulling in packages that exist only on other arches and
marking them as remove, for some dumb reason. I'll have to really dig
into the code and see what's going on here.
If I run "system-config-kickstart anaconda-ks.cfg" it fails
on each of the unknown
packages (e.g., yaboot is below):
Traceback (most recent call last):
File "/usr/bin/system-config-kickstart", line 81, in <module>
kickstartGui.kickstartGui(file)
File "/usr/share/system-config-kickstart/kickstartGui.py", line 180, in
__init__
self.applyKickstart()
File "/usr/share/system-config-kickstart/kickstartGui.py", line 338, in
applyKickstart
self.packages_class.applyKickstart()
File "/usr/share/system-config-kickstart/packages.py", line 255, in
applyKickstart
pkgs = self.y.pkgSack.returnNewestByName(pkg)
File "/usr/lib/python2.5/site-packages/yum/packageSack.py", line 318, in
returnNewestByName
return bestofeach.returnNewestByName(name)
File "/usr/lib/python2.5/site-packages/yum/packageSack.py", line 640, in
returnNewestByName
raise PackageSackError, 'No Package Matching %s' % name
PackageSackError: No Package Matching yaboot
Of course, it shouldn't be crashing like this regardless. I'll add some
handling in for this.
- Chris