I'm not sure if this is an anaconda or a system-config-kickstart error.
I installed fc7t2 from a kickstart file containing the following:
%packages
@admin-tools
@base
@base-x
@core
@editors
@java
@printing
@text-internet
comps-extras
cracklib-dicts
gnome-mime-data
kernel-headers
nash
rmt
tzdata
xkeyboard-config
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
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
If I delete the lines causing errors the utility will start. However, writing back a
new ks.cfg still appends the offending packages.
--
* The Digital Hermit http://www.digitalhermit.com
* Unix and Linux Solutions kwan@xxxxxxxxxxxxxxxxx
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list