Bug 160866 - during custom package selection, selections not always honored (or ignored)
during custom package selection, selections not always honored (or ignored)
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
4
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Paul Nasrat
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-17 17:08 EDT by John William
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-11-28 14:39:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
install.log file (60.91 KB, text/x-log)
2005-06-20 21:30 EDT, John William
no flags Details
anaconda.log file (17.46 KB, text/x-log)
2005-06-20 21:31 EDT, John William
no flags Details
anaconda.syslog file (36.57 KB, text/plain)
2005-06-20 21:32 EDT, John William
no flags Details

  None (edit)
Description John William 2005-06-17 17:08:13 EDT
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.
Comment 1 Paul Nasrat 2005-06-19 18:51:16 EDT
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.
Comment 2 John William 2005-06-20 21:30:50 EDT
Created attachment 115726 [details]
install.log file
Comment 3 John William 2005-06-20 21:31:28 EDT
Created attachment 115727 [details]
anaconda.log file
Comment 4 John William 2005-06-20 21:32:08 EDT
Created attachment 115728 [details]
anaconda.syslog file
Comment 5 John William 2005-06-20 23:54:15 EDT
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.
Comment 6 Paul Nasrat 2005-11-28 14:39:37 EST
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.

Note You need to log in before you can comment on or make changes to this bug.