Hi all! 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): 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? Cu knurd (¹) Note, I tried to explain that (and some other important things) a bit in the section "What do I need to pay attention to when configuring the repositories" that I added to http://rpmfusion.org/FAQ earlier today. I did a lot of other changes on that page as well; please check if everything makes sense and of course feel free to improve it