Description of problem: When I run "debuginfo-install glibc libgcc libstdc++", I get an error regarding 404 rpm.livna.org/mirrorlist-debug not found. I do have rpm.livna.org in my software updates, but do not have debug or source versions (see attached screenshot of what I have set). If I disable rpm.livna.org from this list, debuginfo-install works as expected As I am not asking for an livna debugs, why is debuginfo-install trying to access it (and failing). I did not have this problem in F16 (i686 and x86-64). I am using Xfce for F16 and F17 Version-Release number of selected component (if applicable): yum-utils-1.1.31-4.fc17.noarch How reproducible: 100% Steps to Reproduce: 1. debuginfo-install glibc libgcc libstdc++ 2. 3. Actual results: Loaded plugins: presto, refresh-packagekit enabling rpmfusion-nonfree-updates-debuginfo enabling rpmfusion-nonfree-debuginfo enabling livna-debuginfo enabling rpmfusion-free-updates-debuginfo enabling rpmfusion-free-debuginfo Could not retrieve mirrorlist http://rpm.livna.org/mirrorlist-debug error was 14: HTTP Error 404 - Not Found : http://rpm.livna.org/mirrorlist-debug Cannot find a valid baseurl for repo: livna-debuginfo Expected results: No problems Additional info: Note that it is also enabling all of the rpmfusion stuff, none of which I have set as part of my updates for software Thanks, Paul
Created attachment 625149 [details] screenshot of Software Update Preferences
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.