Bug 669746

Summary:	runnign with -C as non-root tries to create a lockfile in root's cachedir.
Product:	Red Hat Enterprise Linux 6	Reporter:	James Antill <james.antill>
Component:	yum	Assignee:	James Antill <james.antill>
Status:	CLOSED ERRATA	QA Contact:	Karel Srot <ksrot>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	ksrot, tcapek
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	yum-3.2.29-3.el6	Doc Type:	Bug Fix
Doc Text:	When a non-root user ran yum using the "--cacheonly" ("-C") option, yum terminated with a traceback. With this update, yum provides a proper error message in this circumstance.	Story Points:	---
Clone Of:
Clones:	893445 (view as bug list)		Environment:
Last Closed:	2011-05-19 13:34:06 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 James Antill 2011-01-14 15:55:45 UTC

Description of problem:

 yum -C blah ... as a non-root user tries to lock the root cachedir (which tracebacks). Fix is simple, and should be upstream soon.


 Manual clone of: bug#669582

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

yum-3.2.29-1

Comment 5 Tomas Capek 2011-05-17 12:01:04 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When a non-root user ran yum using the "--cacheonly" ("-C") option, yum terminated with a traceback. With this update, yum provides a proper error message in this circumstance.

Comment 6 errata-xmlrpc 2011-05-19 13:34:06 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0602.html