Bug 767380

Summary:	yum -C should consider user cache as well
Product:	[Fedora] Fedora	Reporter:	Ville Skyttä <ville.skytta>
Component:	yum	Assignee:	Seth Vidal <skvidal>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	ffesti, james.antill, jzeleny, maxamillion, pmatilai, tla, vmukhame
Target Milestone:	---	Keywords:	Reopened
Target Release:	---	Flags:	james.antill: needinfo?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-28 12:23:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ville Skyttä 2011-12-13 22:32:13 UTC

With current yum git:

$ sudo yum clean all ; yum clean all ; sudo rm -rf /var/tmp/yum-*

$ ./yummain.py --disablerepo=* --enablerepo=fedora grouplist
[ works, and outputs the group list ]

$ ./yummain.py -d 0 -C --disablerepo=* --enablerepo=fedora grouplist
Setting up Group Process
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again

No such problems when run as root (if the grouplist has been fetched first).

Comment 1 Zdeněk Pavlas 2011-12-14 15:41:06 UTC

This is not a bug.  --cacheonly instructs yum to use the system cache which is empty (cleaned) and read-only.

The error message is misleading (suggests that some URL or path is invalid).  It wraps other, more appropriate error message: "Error: Cannot find repomd.xml file for fedora".

Comment 2 Ville Skyttä 2011-12-14 20:09:00 UTC

In that case the --cacheonly option is silly and should be improved.  The user does have a user specific cache (it was created as a result of the 2nd command), --cacheonly should just use it.  If not, why is the user specific cache created in the first place?

Comment 3 Zdeněk Pavlas 2011-12-15 10:23:37 UTC

> user does have a user specific cache .. --cacheonly should just use it.

It's documented not to do so: "If you're using this as a user yum will not use the tempcache for the user but will only use the system cache in the system cachedir."

> If not, why is the user specific cache created in the first place?

2nd command didn't use the --cacheonly option.  If you run the 3rd command without -C it will/should reuse the user-specific tempcache.

Comment 4 Ville Skyttä 2011-12-15 18:51:50 UTC

2nd command didn't use the --cacheonly option because its only purpose was to create the cache.  Without it, there would be no cache whatsoever because the first cleans both the system and the user caches.

Comment 5 James Antill 2011-12-16 16:50:32 UTC

 I'm thinking about changing this, and the current rawhide+rebuilds:

http://repos.fedorapeople.org/repos/james/yum-rawhide/

...does this, can anyone test and see if their life gets easier (I know of at least one annoyance with it atm. ... but more testing would be welcome).

Comment 6 Fedora End Of Life 2013-04-03 19:44:29 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 7 Valentina Mukhamedzhanova 2014-05-28 12:23:47 UTC

I believe this has been fixed in Fedora 19.