Description of problem: When I %include a file containing a list of packages to be installed, kickstart seems to decide on its own what packages to install. I'll attach my kickstart files soon and also the anaconda-ks.cfg generated during the install. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. In the %pre section of the kickstart file create "/tmp/include-test2.cfg" which is a list of packages to install 2. Use the following lines to define packages in the kickstart file: %packages --resolvedeps %include "/tmp/include-test2.cfg" 3. Compare the packages actually installed to those requested. Additional info:
Created attachment 89290 [details] Kickstart file
Created attachment 89291 [details] list of packages
Created attachment 89292 [details] anaconda-ks.cfg generated during installation
Fixed in CVS
I'm going through Bugzilla closing some bugs that have been marked as Modified for some period of time. I believe that most of these issues have been fixed, so I'm resolving these bugs as Rawhide. If the bug you are seeing still exists, please reopen this report and mark it as Reopened.