Bug 212012 - fedora-release has .repo files which do not longer work
fedora-release has .repo files which do not longer work
Product: Fedora
Classification: Fedora
Component: fedora-release (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Cantrell
Depends On:
  Show dependency treegraph
Reported: 2006-10-24 12:59 EDT by Michal Jaegermann
Modified: 2013-01-09 20:32 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-24 13:22:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2006-10-24 12:59:18 EDT
Description of problem:

Yum configuration files from 'fedora-release-5-5' package have entries

As of this morning an attempt to retrieve such file ends up with
"Access failed: 404 Not Found (/download/mirrors/fedora-core-5)"
and this makes yum to fail.

Yes, _I_ know that URL in this mirrorlist can be replaced by another
one pointing to a script on http://mirrors.fedoraproject.org/ but this
will trip multitudes of existing installations.  One would hope for
a redirection from an old location to the new one or, in the worst case,
an update of fedora-release package before an old URL was gone.
Or this is only a temporary hiccup on http://fedora.redhat.com/?
That URL does exists but a download directory is gone.

An update to fedora-release package cannot work reliably as there
is no way to tell when it will applied in a particular case.

Version-Release number of selected component (if applicable):
Comment 1 Jesse Keating 2006-10-24 13:22:27 EDT
Due to significant load, possibly from a DDoS attack, the redirects that would
have made this work have temporarily been disabled.  This will cause the errors
you're seeing.  Once we sort out the load issues, we'll be able to turn this
back on.  Please be patient.

Note You need to log in before you can comment on or make changes to this bug.