[lug] apt-get errors

[Gary Hodges]

Paul E Condon wrote:

>On Thu, Jan 29, 2004 at 08:01:49AM -0700, Gary Hodges wrote:
>
>>
>>sources.list file referenced the "testing" version.  I ran "apt-get 
>>update" successfully a few times over a few days.  Then I changed 
>>"testing" to "sarge" in the sources.list file and immediately started 
>>getting errors like this:
>>
>>
>>99% [4 Sources gzip 0] [Waiting for headers]
>>gzip: stdin: not in gzip format
>>Err http://non-us.debian.org testing/non-US/non-free Sources
>> Sub-process gzip returned an error code (1)
>>
>>
>>Failed to fetch 
>>http://non-us.debian.org/debian-non-US/dists/testing/non-US/main/binary-i386/Packages.gz  
>>Sub-process gzip returned an error code (1)
>>
>>
>>This morning I replaced "sarge" with "testing" in the sources.list file 
>>but I still get the same errors.  When I run an update it seems like 
>>most of the process works and it is only having problems with a 
>>couple/few packages.  For a few days I thought it must be a problem with 
>>file(s) in the archive(s), but I'm not seeing any recent reports of this 
>>with google.
>>
>>    
>>
>The aliases "stable", "testing" and "unstable" are implemented with links in the
>repository file system. It would be very surprising to me, if they were the 
>source of the problem.
>
>I use sarge and upgrade reqularly to keep up with the latest progress towards an
>official release. I have seen error message similar to what you report, but not
>often. When it happens I rerun apt-get update. Invariably it works on the
>second try. I don't think I ever saw this when I was using Woody. I have always
>it was just one of the features one gets when using pre-release software. Since
>it seems to be self-healing, it is not, IMHO, a release critical flaw.
>

I repeated exactly as I described above on another machine today.  I 
installed woody and then upgraded to sarge.  Maybe something I have 
installed you don't, or maybe I've made the same mistake twice.  I get a 
message after each attempt to run update again to fix the problems, but 
it never does.

W: You may want to run apt-get update to correct these problems
E: Some index files failed to download, they have been ignored, or old 
ones used instead.

Gary