Re: File has unexpected size when using cdn-fastly.deb.debian.org [151.101.228.204] buster repository
On Tue, Oct 01, 2019 at 05:07:30PM +1000, Frederick Zhang wrote:
> Hi all,
>
> I'm currently experiencing some unexpected file size issues with the
> 151.101.228.204 node of cdn-fastly.deb.debian.org. I'd appreciate it if
> you guys can help me figure it out.
>
> The issue can be reproduced via the following command using the buster
> docker image:
>
> $ docker run --rm --tty --interactive --add-host
> 'cdn-fastly.deb.debian.org:151.101.228.204' debian:buster bash
> $ apt-get update
> $ apt-get -y install gdb
> E: Failed to fetch
> http://cdn-fastly.deb.debian.org/debian/pool/main/g/gdb/gdb_8.2.1-2+b1_amd64.deb
> File has unexpected size (3108672 != 3134284). Mirror sync in progress?
> [IP: 151.101.228.204 80]
> Hashes of expected file:
> -
> SHA256:8085c893f3b15a7802a47afb3f9cf819c223624d2bac894a8be5884eb8771ac1
> - MD5Sum:27ac5ace5fed107805cd914bec5a8cd8 [weak]
> - Filesize:3134284 [weak]
> E: Unable to fetch some archives, maybe run apt-get update or try with
> --fix-missing?
>
> I tested the same command in two completely different network
> environments so I reckon it's not a network issue. But weirdly enough,
> if I pull the file using curl, the size and hash of the file look just
> fine.
>
> # still in the docker container, after installing curl
> $ curl -s
> http://cdn-fastly.deb.debian.org/debian/pool/main/g/gdb/gdb_8.2.1-2+b1_amd64.deb
> -o gdb_8.2.1-2+b1_amd64.deb
> $ sha256sum gdb_8.2.1-2+b1_amd64.deb
> 8085c893f3b15a7802a47afb3f9cf819c223624d2bac894a8be5884eb8771ac1
> gdb_8.2.1-2+b1_amd64.deb
> $ du -b gdb_8.2.1-2+b1_amd64.deb
> 3134284 gdb_8.2.1-2+b1_amd64.deb
>
> Can someone shed some light on me? Thanks.
>
Hi,
thanks for pointing this out. It looks like there was an error on our
part where we have two different versions of
pool/main/g/gdb/gdb_8.2.1-2+b1_amd64.deb:
https://snapshot.debian.org/package/gdb/8.2.1-2/#gdb_8.2.1-2:2b:b1
One was built in July for Debian unstable, and the second one for buster
in August. Depending on which cache node you hit, it may have cached
the old version.
We'll try to purge the old files from the CDN, and rebuild gdb for
buster to use a version that avoids the collision.
Cheers,
Julien
Reply to: