Bug 106719

Summary:	-k argument still having problems with relative paths
Product:	[Retired] Red Hat Linux	Reporter:	Pavel Kankovsky <peak>
Component:	up2date	Assignee:	Adrian Likins <alikins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fanny Augustin <fmoquete>
Severity:	low	Docs Contact:
Priority:	medium
Version:	7.3	CC:	gafton, mihai.ibanescu, milan.kerslager
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-08-27 01:19:27 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 Pavel Kankovsky 2003-10-09 20:42:09 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030918

Description of problem:
an ugly child of bug #40834:
up2date cannot handle relative paths in -k argument when it gets multiple
directories separated by colons

Version-Release number of selected component (if applicable):
up2date-2.8.40-3.7.3

How reproducible:
Always

Steps to Reproduce:
1. put some new packages in multiple directories, say i386 and i686
2. run up2date -k i386:i686 -u

Actual Results:  up2date creates a dangling relative symlink in
/var/spool/up2date when it should install a file in the second directory, and
dies complaining it cannot open the symlink (no such file or directory)

Expected Results:  no errors, of course :)

Additional info:

the bug is obvious: os.path.abspath(os.path.expanduser(...)) is done on the
whole list of directories, and only the first component is made absolute

Comment 1 Adrian Likins 2003-10-10 00:52:23 UTC

fixed in cvs / 4.1.7