Bug 585486 - Cannot retrieve repository metadata (repomd.xml) for repository: fedora
Summary: Cannot retrieve repository metadata (repomd.xml) for repository: fedora
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 13
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-24 10:31 UTC by Kinshuk Sunil
Modified: 2014-01-21 23:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-24 10:42:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kinshuk Sunil 2010-04-24 10:31:03 UTC
Description of problem:
I was running Fedora 12. Started updating my Fedora 12 install to Fedora 13 Beta as I was told it had better hardware support for my Dell Inspiron 1564 Laptop.

Started following steps mentioned at: https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum

When I reached step 4, since then any yum commands results in the error message:
"Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again"

I have searched the internet for solutions to these issues. Have already tried the following:
1. Switch baseurl and mirrorlist in my fedora.repo and fedora-updates.repo
2. Added Mirror IPs in my /etc/hosts
3. Added a proxy statement inside my yum.conf (since I am under a proxy)

But neither has solved my issue.

Additional info:
Current Yum.conf - http://fpaste.org/ZYNz/
Current Fedora.repo - http://fpaste.org/qLwE/
Actual Yum Output - http://fpaste.org/zHhp/

rpm -q fedora-release: fedora-release-13-0.7.noarch
rpm -q libproxy: libproxy-0.2.3-12.fc12.i686

Comment 1 Kinshuk Sunil 2010-04-24 10:42:13 UTC
added:
proxy=<ip>:<port>
proxy_username=<my username>
proxy_password=<my password>

and yum is working now. hopefully, will update to Fedora 13 Beta seamless now.


Note You need to log in before you can comment on or make changes to this bug.