Blech, so basically no way around getting rid of it. Any idea why the deployment guide refuses to not install itself? Like I said, I checked after I installed the system for anything that would have been bringing it in, here's what you get: [root@titan ~]# rpm -q --whatrequires system-config-securitylevel-tui no package requires system-config-securitylevel-tui [root@titan ~]# rpm -q --whatrequires Deployment_Guide-en-US no package requires Deployment_Guide-en-US I understand why the system-config-securitylevel-tui gets installed now, but I don't see what's pulling in the Deployment guide. -- sh > -----Original Message----- > From: kickstart-list-bounces@xxxxxxxxxx > [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Chris Lumens > Sent: Thursday, March 13, 2008 8:12 AM > To: kickstart-list@xxxxxxxxxx > Subject: Re: Wrong packages being installed. > > > What am I missing here? Also, > system-config-securitylevel-tui isn't > > being brought in because of a requirement, it's just > showing up. You > > can remove the package as soon as the system comes up. It also > > doesn't show in the anaconda.log as being added to fulfill a > > requirement. It just suddenly shows up in the log, because > slang and > > newt do get added due to a requirement that > system-config-securitylevel has. > > system-config-securitylevel-tui is installed because anaconda > itself needs it to be installed for setting the root > password, configuring the firewall, etc. > > - Chris > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list > _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
