Bug 88843

Summary:	up2date fails to download if install would fail
Product:	[Retired] Red Hat Linux	Reporter:	ratness
Component:	up2date	Assignee:	Adrian Likins <alikins>
Status:	CLOSED NOTABUG	QA Contact:	Fanny Augustin <fmoquete>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9	CC:	gafton, mihai.ibanescu
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-04-15 18:05:34 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 ratness 2003-04-14 20:03:55 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461)

Description of problem:
If I specify the -d flag, up2date should download the packages (which I can 
later install by hand, after massaging the filesystem into a state to where the 
update will take).  Instead, it fails.

Version-Release number of selected component (if applicable):
up2date-3.1.23-1

How reproducible:
Always

Steps to Reproduce:
1. cram /usr to near capacity
2. up2date -d somepackages

Actual Results:  # /usr/sbin/up2date -d glibc glibc-common
[ snip ]
RPM package conflict error.  The message was:
Test install failed because of package conflicts:
installing package glibc-common-2.3.2-27.9 needs 22MB on the /usr filesystem

Expected Results:  packages should be in /var/spool/up2date (which I confirmed 
has free space)

Additional info:

Comment 1 Adrian Likins 2003-04-15 18:05:34 UTC

Yup. Up2date is designed to only let you download packages you
can install (aka, you have space for, no unsolved deps, don't
conflict with other packages, etc)