Hide Forgot
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).
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".
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?
> 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.
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.
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).
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
I believe this has been fixed in Fedora 19.