Yesterday we noticed that puppet is not running properly on our Pis. The root of the cause is this:
```
Err:5 http://raspbian.raspberrypi.org/raspbian buster Release
404 Not Found [IP: 93.93.128.193 80]
```
doing `sudo apt-get update` predictably yields the same result. Following that IP, I can indeed see that the folder http://93.93.128.193/raspbian/dists/buster/ is *empty*, apparently since the 6th of December (4 days ago, which would make sense. We weren't gonna to notice it over the weekend). Bullseye is there, but stretch is also empty, for a couple of years already. This makes me a bit nervous, since it might mean that the buster repo isn't coming back either. Which would be a problem.
Are there any other mirrors we could use?
Updating the system is not an option. I know you want to recommend it, but we're talking hundreds of Pis deployed all over the place here. Some in locations you need a heli or go mountain climbing to get to. We are not going to risk remote-updating them.
```
Err:5 http://raspbian.raspberrypi.org/raspbian buster Release
404 Not Found [IP: 93.93.128.193 80]
```
doing `sudo apt-get update` predictably yields the same result. Following that IP, I can indeed see that the folder http://93.93.128.193/raspbian/dists/buster/ is *empty*, apparently since the 6th of December (4 days ago, which would make sense. We weren't gonna to notice it over the weekend). Bullseye is there, but stretch is also empty, for a couple of years already. This makes me a bit nervous, since it might mean that the buster repo isn't coming back either. Which would be a problem.
Are there any other mirrors we could use?
Updating the system is not an option. I know you want to recommend it, but we're talking hundreds of Pis deployed all over the place here. Some in locations you need a heli or go mountain climbing to get to. We are not going to risk remote-updating them.
Statistics: Posted by b_avisec — Wed Dec 10, 2025 9:36 am