Apt update problem

FlightAware General
1

Hi, all.

Updating my install today and I’m getting this error when receiving the package list on apt update:

E: Failed to fetch http://flightaware.com/adsb/piaware/files/packages/dists/bullseye/piaware/binary-armhf/Packages.gz File has unexpected size (9573 != 9566). Mirror sync in progress?

I usually go through apt-cacher-ng, so I disabled this to double check, but the error still happens.

2

I get this occasionally.
Seems to happen when one of the FlightAware mirrors has a corrupted file. Just wait a while and try again, hopefully you will then get a different mirror server and it will work correctly.

3

yeah I’ve been having this problem too, its been going on for 11 hours now…hoping it’ll be fixed soon, as i’m trying to get a new pi set up and this is getting in the way.

E: Failed to fetch http://flightaware.com/adsb/piaware/files/packages/dists/bookworm/piaware/binary-arm64/Packages File has unexpected size (4665 != 4681). Mirror sync in progress? [IP: 172.64.148.55 443]

4

Yep same problem here. My Pi’s SD card failed last night so setting up a new one - this is stopping me.

5

I also got this error this afternoon after initiating an update: run-apt-get(4817): E: Failed to fetch http://flightaware.com/adsb/piaware/files/packages/dists/bullseye/piaware/binary-armhf/Packages File has unexpected size (9573 != 9566). Mirror sync in progress? [IP: 104.18.39.201 443]

6

anyone from FA have an update on this? been 48 hours and no status change.

7

I’m trying to install this software for the first time, and I’m also experiencing this same issue with a potentially corrupted mirror. This is causing a blocker on the installation process. Digging through the forum history shows that this issue seems to spring up with some frequency, which is a bit worrying :frowning:

8

Yes, still going on here this morning, 03 July.

9

@eric1tran @obj ?

10

i just tried on jul 3 9:34am MDT, the apt update worked successfully

11

This issue is fixed. Sorry for the trouble. Some people were getting an old copy of the apt release files depending on which Cloudflare instance you were hitting

5 Likes
12

Thank you! All working fine now.

13

Many thanks :smile: Everything looks a lot happier at this end now!