Bug 185488 - Yum command error
Summary: Yum command error
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
: 185489 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-15 05:46 UTC by kenneth
Modified: 2014-01-21 22:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-15 05:51:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description kenneth 2006-03-15 05:46:05 UTC
I have a lot of Fedora Core 2 installed. But when I do Yum command in whatever 
list and update. I got the following error. Please help. Thanks

[root@localhost root]# yum list
Gathering header information file(s) from server(s)
Server: Fedora Core 2 - i386 - Base
Server: Fedora Core 2 - i386 - Released Updates
Server: eXtra packages, updates and rt itself
retrygrab() failed for:
  http://campus.fct.unl.pt/paulomatos/rt/repository/headers/header.info
  Executing failover method
failover: out of servers to try
Error getting file 
http://campus.fct.unl.pt/paulomatos/rt/repository/headers/header.info
[Errno 4] IOError: <urlopen error >

Comment 1 Ignacio Vazquez-Abrams 2006-03-15 05:49:59 UTC
*** Bug 185489 has been marked as a duplicate of this bug. ***

Comment 2 Ignacio Vazquez-Abrams 2006-03-15 05:51:02 UTC
This is a problem with your repo info, not yum.

Comment 3 kenneth 2006-03-15 08:55:24 UTC
(In reply to comment #2)
> This is a problem with your repo info, not yum.

How can I set the repo info in order to get it works? It seems all of the 
Fedora Core 2 has suffering from this problem. 

Comment 4 Seth Vidal 2006-03-15 11:42:22 UTC
You have the wrong path to the baseurl:

You probably have:
http://campus.fct.unl.pt/paulomatos/rt/repository/

but you need to have either 3.0.x or 3.4.x on the end to find the repository.

go look at the url in a browser.

If you can't find a 'headers' dir then it won't work.


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