YUM: Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora

[glennzo]

Ashmeel, have you done what I've suggested and tried yum again?

[ashmeel]

Glenzzo, Thanks for ur suggestion but it did not work.

Then I again commented mirrorlist and un-commented baseurl by using this

su -c "sed -i 's|^#baseurl|baseurl| ; s|^mirrorlist|#mirrorlist|' /etc/yum.repos.d/rpmfusion*free*repo"

Now its working...



Thanks again Glenzzo.

Ash.

[glennzo]

Great! Now off to study that sed command. All I know how to do is surf the web and play solitaire

[Silgrin4D]

@posts #12...16:

I am experiencing the same Cannot retrieve repository metadata (repomd.xml) for repository: fedora error while trying to do yum groupinstall "GNOME Desktop Environment". Thus, it is not possible for me to go to System>Administration>etc..

Would be glad to receive some suggestions how to make this jumk work. G4 mac, Fedora 12 (text-based install, no choice). Using ipv4-based network and netinstall CD image (that "beast" does not read "burned" DVDs!) Please use rather detailed and clear language..

[smokewulf]

i am getting same error trying to install nfs server.
my system is not connected to the internet so i can't get updates. also getan error when commenting yum file that says fedora-install-media is not file
need help

[mrmister]

I had the same problem on my work machine (Fedora 12 x64). I thought setting the system proxy would be enough but apparently yum doesn't pick it up and you have to specify the proxy in /etc/yum.conf like this

[main]
cachdir=/var/cache/yum/$basearch/$releasever
...
...
...
installonly_limit=3
proxy=http://path.to.your.proxy.com:80

Hope this helps!

[JetmechAl]

Thank's for the great suggestions..............all.

adding "80.239.156.215 mirrors.fedoraproject.org" to my
/etc/hosts (opened with gedit through terminal with root user)and
adding the quoted line above worked for me .

thanks so much.

fresh install fedora 12 i386

[Pat McClung]

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/04/09/disabling-ipv6-in-rhel-5-4-and-fedora-12/

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

[sej7278]

i don't think it is an ipv6 problem as i already disabled it, and its not dns either i don't think.

only thing that fixed it on my two f12 boxes was "yum clean metadata", which is odd as i'd have thought "yum clean all" would include the metadata!

[Pat McClung]

Yes, it's not really a IPV6 problem. There's a bug in the Fedora MirrorManager code somewhere.
Disabling ipv6 removed the problem for the fedora and the fedora updates repositories on my F12 system.
Still got a problem with the rpmfusion repositories, though.

Yum clean all does clean the metadata.

[TheVoice]

Hello everybody, just signed up with this handle for reasons that should become very obvious to the community.

There seem to be some bright and not so bright users of this operating system. What I have seen a lack of is genius. Anyone who has ever performed maintenance on a machine should know this: You can fix the problem, or you can throw parts at it.

So what is the problem?

It isn't that we cannot receive metadata. That is only a description of the underlying issue, a solution to which is actually dependant on platform, release, initial configuration and current configuration.

From my approach, (a fresh install from official FC12 DVD media) the entire situation is horse crap. After searching the net for similarly "DESCRIBED" issues I found that the actual problem (given a properly functioning network connection) is that ALL REPO Packages are being installed with the BASEURL element of the repo config files commented out. One person who shall remain nameless in the interim happened uppon a stroke of genius or pure experience when he produced a command that does in fact expell CURRENT problems:

su -c "sed -i 's|^#baseurl|baseurl| ; s|^mirrorlist|#mirrorlist|' /etc/yum.repos.d/*repo"

Yay! It works now! Back to setting up my box the way I want it!

WTF?? Cant get meta data for RPM fusion? How is that? I just installed the repo package !!! ... and wait for it... * BINGO *

I would have to say that the problem is either yum, PackageKit, or rpm. Given the fact that this ISSUE produced itself for me 1 out of (at least) 2 times from the same installation media, its not actually a binary problem, its a configuration issue. Somewhere within this software there is a switch that currently says "Only mirrors are worthy install sources, blacklist all auto configured base URI's" elsewhere there is a logic path that says "Get the current repo data from from path: ??? Uh-oh, Path is undefined!, exiting"

The sed command mentioned above, is not the cure for bleeding, it is only a band-aid. Without a new package release, and a support ticket to confirm its expulsion, this problem is not SOLVED. Hehe.. If it was solved, no one would need waste frivolous amounts time and resources to diagnose and correct the problem.

I wish I had the time to waste learning a handicapped language, fixing a handicapped program. Well, actually I don't. Neither do the handicapped users of windows machines, neither do the small business owners and corporations who need 110% uptime. In reality, we need software that works yesterday and today. DEVELOPERS: Keep that in mind when you test your code, put it to rest before you release it.

oh yeah, 1100 fps RADEON HD2400PRO @ radeon drvr. 1500 fps with fglrx drvr, but only works without PAE kernel! Another shining example of a failed attempt at greatness-> AMD/ATI (yay..) U would almost think nobody learns anything from the mistakes of others.

Cheers to the guy who produced the SED code! That sir is a true GEM of coding discipline.

* edit * I did modify the code a bit because the solution was slightly out of context eg: "some-original-file*.repo" to "*.repo" On my machine, the problem occurs with all repositories, foreign and domestic

[fredjaber]

I did this and now I can update with yum update.

edit /etc/hosts and add the following:

80.239.156.215 mirrors.fedoraproject.org
213.129.242.84 mirrors.rpmfusion.org

then from system>preference>netwok proxy, change it to manual proxy configuration and input your network proxy.

restart the system and try to yum update.

This should work

[cx861130]

I had the same problem on my work machine (Fedora 12 x64). I thought setting the system proxy would be enough but apparently yum doesn't pick it up and you have to specify the proxy in /etc/yum.conf like this

[main]
cachdir=/var/cache/yum/$basearch/$releasever
...
...
...
installonly_limit=3
proxy=http://path.to.your.proxy.com:80

Hope this helps!

Oh that worked for me ! Thanks !

[JamesNZ]

I would first disable all the existing repos from PackageKit and then open the terminal and go

yum makecache

[seansai]

I am having some problems of the same but mine looks like this

[root@localhost]# yum update yum
Loaded plugins: langpacks, presto, refresh-packagekit
Adding en_US to language list
adobe-linux-i386 | 951 B 00:00
adobe-linux-i386/primary | 12 kB 00:00
adobe-linux-i386 18/18
fedora/metalink | 20 kB 00:00
fedora | 4.3 kB 00:00
fedora/primary_db | 11 MB 00:13
http://packman.inode.at/suse/14/repodata/repomd.xml: [Errno 14] HTTP Error 404 : http://packman.inode.at/suse/14/repodata/repomd.xml
Trying other mirror.
http://packman.mirrors.skynet.be/pub...ta/repomd.xml: [Errno 14] HTTP Error 404 : http://packman.mirrors.skynet.be/pub...ata/repomd.xml
Trying other mirror.
http://packman.jacobs-university.de/...ta/repomd.xml: [Errno 14] HTTP Error 404 : http://packman.jacobs-university.de/...ata/repomd.xml
Trying other mirror.
http://ftp.uni-erlangen.de/pub/mirro...ta/repomd.xml: [Errno 14] HTTP Error 404 : http://ftp.uni-erlangen.de/pub/mirro...ata/repomd.xml
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/pa...ta/repomd.xml: [Errno 14] HTTP Error 404 : http://ftp.halifax.rwth-aachen.de/pa...ata/repomd.xml
Trying other mirror.
http://ftp.gwdg.de/pub/linux/misc/pa...ta/repomd.xml: [Errno 14] HTTP Error 404 : http://ftp.gwdg.de/pub/linux/misc/pa...ata/repomd.xml
Trying other mirror.
http://packman.unixheads.com/suse/14...ta/repomd.xml: [Errno 14] HTTP Error 404 : http://packman.unixheads.com/suse/14...ata/repomd.xml
Trying other mirror.
http://ftp.gts.lug.ro/packman/suse/1...ta/repomd.xml: [Errno 14] HTTP Error 404 : http://ftp.gts.lug.ro/packman/suse/1...ata/repomd.xml
Trying other mirror.
http://ftp.twaren.net/Linux/Packman/...ta/repomd.xml: [Errno 14] HTTP Error 404 : http://ftp.twaren.net/Linux/Packman/...ata/repomd.xml
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: packman. Please verify its path and try again


I am a complete Newbie, lay man terms please, any suggestions