yum broke Again! no metadata repond.xml

[miles]

"cannot retrieve metadata (repond.xml)

I tried yum clean all, then yum update - restarted until updating rawhide primary_db then broke again

ps: this started after loading rpm http://download1.rpmfusion.org/.... although both free and non free seemed to install correctly

any fixes or workarounds to this ?

sigh - yum continues to be our achillies heel of fedora

[typerlc]

"cannot retrieve metadata (repond.xml)

I tried yum clean all, then yum update - restarted until updating rawhide primary_db then broke again

ps: this started after loading rpm http://download1.rpmfusion.org/.... although both free and non free seemed to install correctly

any fixes or workarounds to this ?

sigh - yum continues to be our achillies heel of fedora

I assume the line you quoted is a typo ... it should be repomd.xml. Anyway, that most likely indicates a problem with your internet connection, or a problem with the mirror that you are accessing. Try connecting to a different mirror.

For what its worth, I feel the opposite ... I think yum is great (though it has its issues occassionally).

[Demz]

whats your repolist? yum repolist in terminal

[miles]

whats your repolist? yum repolist in terminal

Loaded plugins: presto, refresh-packagekit
Killed

doesn't seem good.

[Demz]

my guess is that you've installed the wrong RPMFusion rpm into F12 you could do this

rpm -qa|grep rpmfusion

[miles]

my guess is that you've installed the wrong RPMFusion rpm into F12 you could do this

rpm -qa|grep rpmfusion

I searched some more and found that I had to specify rpmfusion using rawhide not stable - that solved the problem.

In ubuntu they make the repositories based on the release - that seems to make more sense than a continuous rawhide which means changing back to stable after the release - just my $.02

[Demz]

so in essence you had the wrong RPM as i stated, read before you actually install something that may end up stuffing up your yum

[RahulSundaram]

Miles,

You might be interested in

https://fedoraproject.org/wiki/No_Fr...whide_Proposal

[miles]

Miles,

You might be interested in

https://fedoraproject.org/wiki/No_Fr...whide_Proposal

thks - It's good that problem is being addressed - but I'm not sure it's the right way. I guess I'm suggesting that instead of rawhide that it simply be the repository for the next release - this would allow branching off to the next release at the appropriate time, meanwhile the trunk stays as the upcoming release. Then repository names thru alpha, beta, release all stay the same.

Anyway fodder for another thread sometime.

[RahulSundaram]

Hi,

You seem to be confused. What you are suggesting is what is being implemented already.

[miles]

Hi,

You seem to be confused. What you are suggesting is what is being implemented already.

I happen to think it's the other way around Right now for F12 the repositories are "rawhide" Upon stable release, I believe the repositories branch and to stay with F12, the repositories get renamed stable while the rawhide repositories go off towards F13. This means I have to rename my fusion repositores as stable rather than rawhide. I'm suggesting the current repositores be named F12 - then they don't have to be renamed stable upon F12 release meanwhile the next branch gets named F13 "ie no more rawhide" This is the way Ubuntu seems to do it and we found it easy to keep on the right repositories. The confusion in naming is what led to this thread.

I guess it's just a trade-off for those who always want to stay on cutting edge don't have to change repo names with different versions with rawhide vs those who move from beta(rawhide) to stable (and then maybe back to beta on another version)

[RahulSundaram]

Hi,

FYI, I am a Fedora contributor. I would suggest reading in detail the link already provided by me. What you are suggesting is what is already being implemented. Current process to switch repositories automatically is described at

http://fedoraproject.org/wiki/Upgrad...lease_to_final

This automatic transition happens for RPM Fusion as well by updating the rpmfusion-release package just before the release so this won't actually affect end users at all. No manual switching is ever necessary.

From Fedora 13 onwards

https://www.redhat.com/archives/fedo.../msg01013.html

Hope that helps.

[Jongi]

Ah so it is going the way of Debian does it with Sid?

[RahulSundaram]

Hi,

Not sure what that means.

[Jongi]

Debian has an unstable branch called Sid. So if you point your repos to this repo, you effectively never run the official release versions of Debian.