Bug 134504

Summary:	Unresolved dependancies are ignored
Product:	Red Hat Enterprise Linux 3	Reporter:	Matt Sturtz <msturtz>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED WONTFIX	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	nobody+pnasrat
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-10-04 12:47:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matt Sturtz 2004-10-04 05:02:16 UTC

I have merged latest updates to AS3 from RHN into our network-based 
install image.  I then ran genhdlist.  When installing on a new 
server, everything installed OK, but when the system rebooted it 
said /etc/inittab was missing.

After booting rescue and looking at install.log, it turned out a new 
dependancy on laus-libs was introduced by several updated packages, 
but it was unresolved.  Anaconda installed anyway without any 
warnings.

The installer should have presented a warning of some kind.

Version-Release number of selected component (if applicable):
Installer from AS3 distro CD

How reproducible: Always

Steps to Reproduce:
1.  Convince Anaconda to install a package (A) which depends on 
another package (B).  This can be via kickstart and/or modifying 
comps.xml and/or introducing a new dependancy to an existing package.
2.  Place package A in /installsource/RedHat/RPMS.  Package B should 
not exist here.
3.  Proceed with install as normal.

Actual Results:  Package A will be installed, and package B will not, 
even though A depends on B.

Expected Results:  Anaconda installer should have refused to continue 
with unresolved deps.

Comment 1 Jeremy Katz 2004-10-04 12:47:10 UTC

This is completely intentional.  Unresolved dependencies get noted on
tty3, but in general, anaconda assumes and requires a well-formed (ie,
all dependencies are resolved) installation tree.