Description of problem: We use repoclosure command for one test in AutoQA and we have found it to behave strangely: https://fedorahosted.org/autoqa/ticket/214 I investigated more and repoclosure behaves really erratically. On my workstation, this is the output under root (notice wrong repo path, using file paths instead of URLs): # repoclosure --tempcache --newest --repofrompath=target,http://download.fedoraproject.org/pub/fedora/linux/updates/13/x86_64 --repoid=target --repofrompath=parent1,http://download.fedoraproject.org/pub/fedora/linux/releases/13/Everything/x86_64/os --repoid=parent1 Added target repo from /root/http:/download.fedoraproject.org/pub/fedora/linux/updates/13/x86_64 Added parent1 repo from /root/http:/download.fedoraproject.org/pub/fedora/linux/releases/13/Everything/x86_64/os Reading in repository metadata - please wait.... Cannot retrieve repository metadata (repomd.xml) for repository: parent1. Please verify its path and try again Some dependencies may not be complete for this repository Run as root to get all dependencies or use -t to enable a user temp cache Checking Dependencies Cannot retrieve repository metadata (repomd.xml) for repository: parent1. Please verify its path and try again And this is the output of the *same* command under common user: $ repoclosure --tempcache --newest --repofrompath=target,http://download.fedoraproject.org/pub/fedora/linux/updates/13/x86_64 --repoid=target --repofrompath=parent1,http://download.fedoraproject.org/pub/fedora/linux/releases/13/Everything/x86_64/os --repoid=parent1 Added target repo from /home/kparal/tmp/http:/download.fedoraproject.org/pub/fedora/linux/updates/13/x86_64 Added parent1 repo from /home/kparal/tmp/http:/download.fedoraproject.org/pub/fedora/linux/releases/13/Everything/x86_64/os Reading in repository metadata - please wait.... Checking Dependencies Repos looked at: 2 parent1 target Num Packages in Repos: 21551 package: 4:perl-5.10.1-112.fc13.i686 from parent1 unresolved deps: perl-libs = 4:5.10.1-112.fc13 ...output clipped... I have another machine (VM) with Fedora 13 where the aforementioned command doesn't work neither under root nor under common user, same problem. When I downgrade to: yum-metadata-parser-1.1.4-1.fc13.x86_64 yum-utils-1.1.26-1.fc13.noarch yum-3.2.27-4.fc13.noarch then repoclosure seems to work on both machines, under any user. But again, it is really erratic, I haven't found a real pattern. Version-Release number of selected component (if applicable): anaconda-yum-plugins-1.0-5.fc12.noarch PackageKit-yum-0.6.6-1.fc13.x86_64 PackageKit-yum-plugin-0.6.6-1.fc13.x86_64 yum-3.2.28-1.fc13.noarch yum-metadata-parser-1.1.4-1.fc13.x86_64 yum-plugin-changelog-1.1.28-1.fc13.noarch yum-plugin-downloadonly-1.1.28-1.fc13.noarch yum-presto-0.6.2-1.fc13.noarch yum-utils-1.1.28-1.fc13.noarch How reproducible: randomly, it seems I can reproduce the problem on my machines
Closed upstream with this patch: http://yum.baseurl.org/gitweb?p=yum-utils.git;a=commitdiff_plain;h=92ea5b33601015d9b2fb009f5ebd2aac6b6dd2df it'll be in the next yum-utils out for fedora* thanks