Eugene V. Lyubimkin wrote:

> Firstly, I would like to confirm that even in that case, the whole update
> thing is run fully, because the next lines should indicate downloading
> Packages.gz for the same entry and succeed (or, hm, possibly, fail too).
> Is it the case?

Oh!  Yes, that’s right; it succeeds.

Get:1 http://ftp.us.debian.org/debian sid Release
Get:2 http://ftp.us.debian.org/debian experimental Release
Get:3 http://ftp.egr.msu.edu/debian sid Release
Get:4 http://ftp.us.debian.org/debian experimental Release.gpg
Get:5 http://ftp.us.debian.org/debian sid Release.gpg
100% [4 experimental Release.gpg 835B/835B 100%][5 sid Release.| 76.5KiB/s | 
ETA: 0s
W: gpg: 
'/var/lib/apt/lists/ftp.us.debian.org_debian_dists_experimental_Release': bad 
signature: 9AA38DCD55BE302B Debian Archive Automatic Signing Key (5.0/lenny) 
<ftpmas...@debian.org>
W: signature verification for 'experimental Release' failed
Get:6 http://ftp.egr.msu.edu/debian sid Release.gpg
Get:7 http://ftp.us.debian.org/debian experimental/main Packages.bz2 [254KiB]
54% [7 experimental/main Packages.bz2 0B/254KiB 0%]            | 77.9KiB/s | 
ETA: 2s
W: downloading 
http://ftp.us.debian.org/debian/dists/experimental/main/binary-i386/Packages.bz2
 failed: invalid size: expected '260345', got '260479'
Get:8 http://ftp.us.debian.org/debian experimental/main Packages.gz [314KiB]
[...]

Trying ‘cupt update’ again:

Get:1 http://ftp.us.debian.org/debian sid Release
Get:2 http://ftp.us.debian.org/debian experimental Release
Get:3 http://ftp.egr.msu.edu/debian sid Release
Get:4 http://ftp.us.debian.org/debian sid Release.gpg
76% [3 sid Release 28.0KiB/101KiB 28%][4 sid Release.gpg 835B/8| 57.0KiB/s | 
ETA: 0s
W: gpg: '/var/lib/apt/lists/ftp.us.debian.org_debian_dists_sid_Release': bad 
signature: 9AA38DCD55BE302B Debian Archive Automatic Signing Key (5.0/lenny) 
<ftpmas...@debian.org>
W: signature verification for 'sid Release' failed
Get:5 http://ftp.us.debian.org/debian experimental Release.gpg
Get:6 http://ftp.egr.msu.edu/debian sid Release.gpg
100% [5 experimental Release.gpg 835B/835B 100%]               | 77.5KiB/s | 
ETA: 0s
W: gpg: 
'/var/lib/apt/lists/ftp.us.debian.org_debian_dists_experimental_Release': bad 
signature: 9AA38DCD55BE302B Debian Archive Automatic Signing Key (5.0/lenny) 
<ftpmas...@debian.org>
W: signature verification for 'experimental Release' failed
Get:7 http://ftp.us.debian.org/debian sid/main Packages.bz2 [6495KiB]
4% [7 sid/main Packages.bz2 0B/6495KiB 0%]                  | 25.0KiB/s | ETA: 
1m47s
W: downloading 
http://ftp.us.debian.org/debian/dists/sid/main/binary-i386/Packages.bz2 failed: 
invalid size: expected '6651138', got '6650451'
Get:8 http://ftp.us.debian.org/debian sid/main Packages.gz [8542KiB]
3% [8 sid/main Packages.gz 0B/8542KiB 0%]                      | 403B/s | ETA: 
2m49s
W: downloading 
http://ftp.us.debian.org/debian/dists/sid/main/binary-i386/Packages.gz failed: 
invalid size: expected '8747079', got '8747611'
Get:9 http://ftp.us.debian.org/debian sid/main Packages [30.4MiB]
1% [9 sid/main Packages 0B/30.4MiB 0%]                        | 452B/s | ETA: 
10m16s
W: failed to download index for 'sid/main'
W: downloading 
http://ftp.us.debian.org/debian/dists/sid/main/binary-i386/Packages failed: 
HTTP response code said error: 404

So it looks like the Release is temporarily “out of sync” with other files.

Meanwhile, I have never run into this problem with apt-get.

... ah, okay, maybe this is it: ftp.us.debian.org uses round-robin DNS
to switch between multiple mirrors.  APT’s HTTP method copes with this
by doing the lookup once and reusing the IP for a number of requests,
whereas it looks like cupt is switching between mirrors too often.

Selecting a random particular mirror (like mirrors2.kernel.org, the
first one ‘ping’ gave me) does avoid the problem, though that doesn’t
rule out this having just avoided some particular problematic mirror.

Regards,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to