Hi All,

I'm getting these errors when trying to update my packages through yum on a Centos 5.2 box:

http://mirror.centos.org/centos/5/os...ta/repomd.xml: [Errno -1] Error importing repomd.xml for base: Damaged repomd.xml file
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: base. Please verify its path and try again


I've tried googling and looking at other people's similar problems. I have another box, a Centos 3.4 box that runs yum just fine.

The address you have in your repo file is incorrect. You say you are running C5.2 but your repo file is pointing to C5. If that colon(on the end of the address above) is in your repo file it may also be causing problems.

I find it neccessary to update this thread with a method I have just used to sort this issue.
1. Backup any repo file you have created incase you need it later, then run yum clear all (as an administrator/root), then create the cache file afresh with yum -y makecache
Restore your backed up repo files and you will be good to go. The Error should disappear.

I hope this will help you.

Emadau

Would you believe it's an ipv6 problem?
I'm running F12 X86_64 upgraded from F11.
The Yum problem [Cannot retrieve repository metadata (repomd.xml)] began after the F12 update and after the first yum update (installed 78 packages and updated 1742 more). THEN the (repmod.xml) problem.
I'm running off a ipv4 router so, have ipv6 disabled (I thought). But, in F12 it's different than in F11, it seems. So, here's what I did that disabled ipv6, and fixed the YUM problem. You don't need to modify /etc/hosts and all that other stuff above that didn't work for me.
1. disable the ipv6 firewall service [ipv6tables]
2. keep it off - #/sbin/chkconfig ip6tables off
3. Create a file under /etc/modprobe.d (e.g. “blacklist-ipv6.conf”) with the following 2 lines, in the order shown:
install ipv6 /bin/true
blacklist ipv6
4. add the following line to /etc/sysconfig/network
NETWORKING_IPV6=no
(mine had IPV6=no - that don't work, but I left it in there, too)
5. reboot YUM should work fine.
---------------here's the "remove ipv6" reference-------------
http://eldapo.lembobrothers.com/2010...and-fedora-12/

Think normal human beings will ever be able to use Fedora?

1 members found this post helpful.

this same problem still exists with Fedora13. I followed patmcclung's solution to the letter and it worked! Thanks pat.

The question I have, is how vulnerable is my firewall for normal internet invasion now that I have followed this remedy?

patmcclung : You saved my day ....
Disabling IPV6 works for me. I have installed fresh Fedora 14 (32 bit), and problem starts here. i googled up lots of things,
added mirror IPs in /etc/hosts file -- didn't work
Commenting/uncommenting the baseurl and mirrorlist line in files under /etc/yum.repos.d/ -- didn't work

Thank you

you do know that 14 has been UNSUPPORTED for many many many YEARS!!!!!

install the current Fedora 23
yes you are NINE VERSIONS AND 4 YEARS out of date


that is because 14 is 9 VERSIONS out of date
the repos for 14 moved or were deleted YEARS AGO


14 is unsupported
-- DO NOT USE ---

??? Why ????

none of the guides or instructions nor any of the documentation tell you to edit THAT file to set locations for yum


or

install the currently supported CentOS 6.7 if this is OLD hardware

Yes, its out of date but it's a specific requirement to run a legacy software [in house developed] on that version of fedora. No other intention to install outdated version of fedora. By the way i installed it as a virtual machine.

It didn't work for me.

What i googled up, i didn't find that info.

the old and NOT updated and missing all the last 4.5 years of security updates
old fedora 14 rpms are in the historical archive

https://archives.fedoraproject.org/p...x/releases/14/

the very LAST updates are
https://archives.fedoraproject.org/p...ux/updates/14/

mind you this is only for the BASE fedora repo
there are NO!!!! thirdparty archives

you need to set the repo files in /etc/yum/repos.d to use the historical archive

BUT

Warning:
they have not been updated since Dec. 2011
and are missing the last 4 years of security updates

1 members found this post helpful.