From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description of problem: When performing a custom package install (clean install) some of the package selections seem to get "lost" or "ignored". Two machines seemed to have problems with ignored the de-select of vi and selection of emacs. I can understand packages being re-selected for install to satisfy some dependency, but I cannot see a reason why a package would not be installed after being selected (emacs). Version-Release number of selected component (if applicable): How reproducible: Sometimes Steps to Reproduce: 1. Perform install, select custom to manually select packages. 2. After installation, carefully compare packages actually installed to packages selected during install process. Actual Results: The two lists are different, with the most troubling differences being that some packages selected to be installed were not. Expected Results: Packages selected (or de-selected) should be honored. In particular, if there is a good reason why a package cannot be installed then inform the user, but I thought the installer just added packages to satisfy dependencies. Additional info: Marking priority as low as it's annoying, but the packages can then be added/removed once the system is running. Fortunately, I have not seen this problem effect any critical packages.
Could you attach the /root/install.log, /var/log/anaconda.log and /var/log/anaconda.syslog and the actual packages you selected of an affected system.
Created attachment 115726 [details] install.log file
Created attachment 115727 [details] anaconda.log file
Created attachment 115728 [details] anaconda.syslog file
I spent a fair amount of time selecting (and de-selecting) packages for this particular machine's install so I can't give a detailed add-and-removed list, but I specifically selected emacs (under Editors) as one of the last things before proceeding with the installation. That's how I noticed the problem to begin with.
Package selection is being completely redone for FC5. Closing this bug out as we won't be using the code paths which would have hit this.