On Sun, Nov 09, 2008 at 05:32:56PM +0100, Thorsten Leemhuis wrote:
I regularly see reports that RPM Fusion or Livna repositories are not
working; the error reports contain output like this (obviously taken
from a livna report; but I've seen similar reports for RPM Fusion
already):
>
http://rpm.livna.org/fedora/9.93/i386/repodata/repomd.xml: [Errno 14] HTTP Error
> 404: Not Found
> Trying other mirror.
[...]
What's wrong here? Well, the answer is simple: The user is running
rawhide (relver is 9.93 there right now), but he has those the repos
enabled that you should use when you are running a stable Fedora release
(e.g. rpmfusion-{non,}free{-updates}) instead of RPM Fusion's rawhide
repos.
IOW: the user configured something wrongly, but he thinks it's our
fault(ยน).
That afaics happens so often that I started to wonder: Is there anything
we can do to prevent the problem at all? Or a way to make it easier for
users to do the right thing?
Putting a symlink in place that points to the development repos might
circumvent the problem (but maybe yum gets confused if it sees the exact
same repodata twice; and worse: I fear that mirrormanager will get
confused/needs changes as well). Does anyone have a better idea to
prevent that users don't run into this trouble?
I have created repository redirects in mirrormanager. If now someone
requests the mirrorlist for the 9.93 version he/she gets the rawhide
repository list.
(and I really hope that I did not break anything else)
Adrian