Bug 209966 - --ignoremissing is ignored
Summary: --ignoremissing is ignored
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Chris Lumens
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-09 04:02 UTC by Colin Coe
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-03-16 18:32:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Colin Coe 2006-10-09 04:02:33 UTC
Description of problem:
In ks.cfg, --ignoremissing is ignored

Version-Release number of selected component (if applicable):
RHEL5 CLient BETA1

How reproducible:


Steps to Reproduce:
1. Expand installation tree onto hard disk
2. Remove 'cairo-java' packages as they are currently broken.
3. Point client at ks.cfg containing --ignoremissing and using install tree 
created above
4. attempt install
  
Actual results:
An error occurs saying package is missing, retry or abort.

Expected results:
Install should have progressed ignoring the missing packages

Additional info:

Comment 1 Jeremy Katz 2006-10-09 15:19:41 UTC
Did you regenerate the metadata for the repository?

--ignoremissing only says to ignore packages which are specified in %packages
which are not present in the tree metadata.

Comment 2 Colin Coe 2006-10-09 22:07:46 UTC
Ahh, my mistake.  I went looking for the anaconda docs and found that they still
referred to comps.xml not the yum .xml.gz files.  Where are the updated docs?

Comment 3 Chris Lumens 2007-03-16 18:32:31 UTC
I've updated the documentation that ships with anaconda on the HEAD CVS branch.
 This is the source for the documentation on the website.  I don't think they
pull updated documentation at any point during the update cycle, though.  I'll
close this one out as NEXTRELEASE for now.  If it's really critical, reopen and
we can reassign to the docs team to see what they think.


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