Re: apt update broken for days?
On Fri, Jan 18, 2002 at 08:46:18AM -0600, Ron Johnson wrote:
> Have you tried a different mirror? It's been working perfectly on
> my system, even though I do get non-us from non-us.debian.org.
>
> It does, though, sound like there's something wrong with your system.
> Maybe a corrupt .deb file somewhere?
>
> On 18 Jan 2002 09:22:49 -0500 "Paul Smith"<pausmith@nortelnetworks.com> wrote:
> > I haven't been able to do an apt-get update successfully for three or
> > four days now; does anyone know what's going on?
> >
> > I get these failures every time I try:
> >
> > gzip: stdin: invalid compressed data--format violated
> > Err http://non-us.debian.org testing/non-US/main Sources
> > Sub-process gzip returned an error code (1)
> > ...
> > gzip: stdin: not in gzip format
> > Err http://http.us.debian.org testing/contrib Packages
> > Sub-process gzip returned an error code (1)
> > ...
> > gzip: stdin: not in gzip format
> > Err http://http.us.debian.org testing/main Sources
> > Sub-process gzip returned an error code (1)
> > ...
> > gzip: stdin: not in gzip format
> > Err http://http.us.debian.org testing/non-free Sources
> > Sub-process gzip returned an error code (1)
> > ...
> > gzip: stdin: not in gzip format
> > Err http://http.us.debian.org testing/contrib Sources
> > Sub-process gzip returned an error code (1)
> > ...
> > gzip: stdin: not in gzip format
> > Err http://http.us.debian.org unstable/main Packages
> > Sub-process gzip returned an error code (1)
> > ...
> > gzip: stdin: not in gzip format
> > Err http://http.us.debian.org unstable/non-free Packages
> > Sub-process gzip returned an error code (1)
> > ...
Maybe its the FBI snaffling traffic to insert magic lantern on your system. And doing a bad job of it.
When is apt going to support https???
Crispin
Reply to: