I successfully ran an update on 12 October. ATT it reported Bullseye was changing to ‘oldstable’ as the official Pi OS release of Bookworm is now ‘stable’. My guess is an updated release file is needed/missing for the Bullseye transition to oldstable. Quite sure they will get it sorted out in the near future. And yes, I am getting the same errors too despite my recent update.
This is a problem on our side, the mirrors are meant to be excluded from http → https redirect for exactly this reason but that rule has been lost somewhere. I’ve asked ops to take a look. Sorry for the hassle!
I’ll tell you when it is fixed Just had to reinstall one of my feeders due to a catastrofic filesystem crash so I only have one that needs a correction then and I will post here if it is needed
I don’t think we need to do anything while it works. I guess they just have a mess in their web service config. Files pointed by this chage are the same.
Then submit the following command sudo apt update && sudo apt full-upgrade -y
The results will be similar to
pi@cs1:~ $ sudo apt update && sudo apt full-upgrade -y
Hit:1 http://repo.feed.flightradar24.com flightradar24 InRelease
Hit:2 https://www.flightaware.com/adsb/piaware/files/packages bullseye InRelease
Hit:3 Index of /debian bullseye InRelease
Get:4 Index of /raspbian bullseye InRelease [15.0 kB]
Fetched 15.0 kB in 2s (9,438 B/s)
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
All packages are up to date.
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
pi@cs1:~ $