Is anyone besides me seeing errors like the ones below with "apt-get update"?
Some examples:
Code:
gzip: stdin: not in gzip format
Err http://www.backports.org sarge-backports/main Packages
Sub-process gzip returned an error code (1)
gzip: stdin: not in gzip format
Err http://security.debian.org stable/updates/main Packages
Sub-process gzip returned an error code (1)
gzip: stdin: not in gzip format
Err http://ftp.debian.org testing/main Packages
Sub-process gzip returned an error code (1)
The repos I'm seeing these errors with are:
Code:
http://security.debian.org stable/updates/main Packages
http://www.backports.org sarge-backports/main Packages
http://ftp.debian.org testing/main Packages
http://ftp.debian.org testing/contrib Packages
http://ftp.debian.org testing/main Sources
http://ftp.debian.org testing/contrib Sources
http://ftp.debian.org unstable/main Packages
http://ftp.debian.org unstable/contrib Packages
http://ftp.debian.org unstable/main Sources
http://ftp.debian.org unstable/contrib Sources
I'm running Sarge on the computer seeing these errors and rarely rarely every pull a package from testing or unstable or backports, so those errors are not a show-stopper, but I'm more concerned about the error on security.debian.org
I've run the apt-get update multiple times and trapped the output to files and the errors are always on these same repos, other repos are OK, so I don't think it's an
intermittant network issue on my end. I watched freespace in /var while running the update and it never dropped below 750Mb free, so plenty of space available.
At home I run Sid, and I am
not seeing these errors on "http://ftp.debian.org unstable/main Packages" for example. This is one of the same repos that are giving me trouble on the other computer. This seems to indicate something different about the network connection from work (the computer with problems) and home (no problems). But I'm not sure what.
