YUM still not accessible

[dr john gardiner]

Thanks for that information. Yes, I looked through the archives but the 
previous yum problems (June/July) seemed to be basically to do with the 
server.

I have changed my yum.conf file so that it has the same urls as at the 
duke site (it had addresses which were slightly different...). [Did 
this as root and then checked by reading the file as as user that the 
changes were saved OK etc..]

BUT, now I get a different error - it says it is gathering package info 
and getting headers, but then says "IOError - #2 - no such file or 
directory", whether I try just "yum", "yum list" or "yum update"

 From the Duke site of repositories there are only the two that are for 
YDL - and I am now definitely using these in my yum.conf.

Any ideas what the error now is  (still, all network and internet 
activity is fine, so there is still not any other hardware or network 
problem at this end, and I guess the servers must be fine as have tried 
several days).

presumably it is something else trivial - thanks

john

On Saturday, August 9, 2003, at 01:13 AM, 
yellowdog-newbie-request@lists.terrasoftsolutions.com wrote:

> Message: 2
> Date: Fri, 8 Aug 2003 13:22:36 -0500
> Subject: Re: How to get YUM working?
> From: Dan Wilson <leapoffaith@mac.com>
> To: yellowdog-newbie@lists.terrasoftsolutions.com
> Reply-To: yellowdog-newbie@lists.terrasoftsolutions.com
>
> You might have to refresh (or create) entries in  /etc/yum.conf.
>
> In case you weren't aware of it, there's a terrific list of YUM
> repositories at http://linux.duke.edu/projects/yum/repos/ Just click on
> one and then cut & paste into /etc/yum.conf.
>
>>
>>> What is wrong? I am connected a LAN via ethernet. Other web activity
>>> and downloads etc work fine via Mozilla.
>>
>> John, I seem to remember a thread about this a month or two ago. You
>> should
>> check the archives and see how it got fixed. I seem to remember
>> problems
>> with YDL's site had something to do with it. There was mention of a
>> change
>> to one of the config files for which server to use.
>
>