Red Hat Bugzilla – Bug 448501
Anaconda does not use excludepkgs in kickstart repo command
Last modified: 2009-02-16 15:32:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/20080418 Ubuntu/7.10 (gutsy) Firefox/220.127.116.11
Description of problem:
When you use a kickstart file with additional yum repositories added to it with the repo command (as described in http://fedoraproject.org/wiki/Anaconda/Kickstart), the excludepkgs option is not used by anaconda.
The excludepkgs option is also omitted from the /root/anaconda-ks.cfg file after a kickstart install.
It could be that I'm just being daft :-) , but if I look at the anaconda source I can't see any evidence that the repo options "excludepkgs", "includepkgs" and "priority" as specified in http://fedoraproject.org/wiki/Anaconda/Kickstart actually exist as valid options.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a kickstart file and add an additional yum repository and specify some packages to be excluded. For example:
repo --name=Update --baseurl=http://download.fedora.redhat.com/pub/fedora/linux/updates/9/i386/ --excludepkgs=kernel
2. Perform a kickstart install with anaconda with the kickstart file just created.
The kernel package from the update repo is used.
I would expect that the kernel package from the update repo is not used and that the kernel package from another repo is used.
Oops, that's because --excludepkgs and --includepkgs was only ever added for
distribution build tools. The next build of anaconda should support this,
though I have not yet tested it for correctness. If you have the capability to
test out rawhide, please give it a spin.