Red Hat Bugzilla – Bug 337411
anaconda does not recognize package selection in kickstart file
Last modified: 2014-03-16 23:09:06 EDT
Description of problem:
I'm installing using a kickstart file, but there are a number of unexpected
1) During installation, anaconda shows a dialog box stating that the package
name samba-swat is unknown. I instruct anaconda to just ignore this package.
2) After installation a large number of gnome related packages are installed,
even though I did not request that in the kickstart file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
After installation, I'm able to manually install samba-swat, using the command:
yum install samba-swat
After installation, the following gnome-related packages are installed:
[root@mij-6 mij]# rpm -q -a | grep gnome
Since the package name in the kickstart file is correct, I expect anaconda to
install it without complaints.
Since I'm running Fedora as a headless server, I do not expect packages like
nodoka-theme-gnome and gnome-themes etc. to be installed.
My kickstart file is attached.
Created attachment 230811 [details]
(1) Please attach /var/log/anaconda* to this bug report so we can see what might
be going on regarding samba-swat.
(2) I'm pretty sure you are getting all those gnome-related packages because you
asked to install the admin-tools group which includes many of the
system-config-* packages, some of which have very complex library requirements.
Most of the packages you listed are just providing libraries. The remainder
are being pulled in as requirements of the first set.
Created attachment 231631 [details]
Created attachment 231641 [details]
I've added the requested attachments.
Not only is samba-swat not found, but system-config-securitylevel-tui isn't
either. Do these packages exist on your hard drive installation media?
Geez, I just checked, and the packages you mention are not there. I'm using
Fedora-7.92-i386-DVD.iso as my hard drive installation media.
So, I guess this is not a bug, unless those packages were meant to be present in
the iso file.
And I've removed the admin-tools group from the package selection in the
kickstart file, and that eliminates a bunch of the gnome packages. The remaining
ones are dependencies caused by the BlueTooth package bluez-utils. Once that
package is removed (I don't need bluetooth support), a lot of supporting
packages can be deleted:
[root@mij-6 mnt]# rpm -e bluez-utils
[root@mij-6 mnt]# rpm -e gnome-vfs2 gnome-mount libgnome NetworkManager-openvpn
NetworkManager-vpnc PolicyKit-gnome libbonoboui libgnomeui gnome-vfs2-obexftp
It would be nice, if the bluez-utils package did not pull in all these gnome
libraries, or alternatively, was not included by default in the "Base" group.
Your comment about bluez-utils is a comps problem, as it does all the grouping.
I'm not seeing where bluez-utils requires parts of the GNOME stack.