Bug 212012 - fedora-release has .repo files which do not longer work
Summary: fedora-release has .repo files which do not longer work
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-release
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Cantrell
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-24 16:59 UTC by Michal Jaegermann
Modified: 2013-01-10 01:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-24 17:22:27 UTC


Attachments (Terms of Use)

Description Michal Jaegermann 2006-10-24 16:59:18 UTC
Description of problem:

Yum configuration files from 'fedora-release-5-5' package have entries
like:
mirrorlist=http://fedora.redhat.com/download/mirrors/fedora-core-$releasever

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):
fedora-release-5-5

Comment 1 Jesse Keating 2006-10-24 17:22:27 UTC
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.