While playing around with Kickstart on RHEL5, I discovered that anaconda
seems to be not calculating dependencies completely correctly.
I have a kickstart file with the following %packages section:
%packages
(no entries)
On RHEL5 Client, this seems to implicitly result in both the 'base' and
'core' package groups being installed.
I compared the resulting installation with what yum calculates as the
resulting install set when just 'base' and 'core' are installed. The set
of packages is identical except that yum wants to install one more
package:
hicolor-icon-theme
which is required by the 'gtk2' RPM. Indeed:
# rpm -q --whatrequires hicolor-icon-theme
but anaconda did not install it:
# rpm -q --whatprovides hicolor-icon-theme
no package provides hicolor-icon-theme
I can install it by hand, and then I am unable to uninstall it (since it
is a requirement of the gtk2 package).
I'm curious if this is an anaconda/yum bug or something specific to my
kickstart environment. I copied the set of RHEL5 Client CD images into a
single install path as per usual.
Client/repodata/primary.xml.gz seems to include the correct dependency
information for the 'gtk2' package, so I don't know why anaconda didn't
install the 'hicolor-icon-theme' RPM. Ideas?
Thanks,
Chris Wing
[EMAIL PROTECTED]
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
