Closed DrCWO closed 1 month ago
Looks like an issue with the specific apt mirror of Armbian. You can wait and hope they will fix the missing release file as it seems to be missing for Bookworm as well.
Do you have the chance to ping the Armbian guys and point them to this issue?
Looks like they fixed it already. At least I can see release file again
Thank you for your effort. I also recognized today that it works again š
Update to latest DietPi, which replaces the Armbian APT server with our own.
Great news š
Creating a bug report/issue
Required Information
DietPi version |
cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=8 G_DIETPI_VERSION_SUB=8 G_DIETPI_VERSION_RC=1 G_GITBRANCH='master' G_GITOWNER='MichaIng'Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
bullseyeKernel version |
uname -a
Linux rooExtend 5.15.52-rockchip64 #22.05.4 SMP PREEMPT Mon Jul 4 09:40:29 CEST 2022 aarch64 GNU/Linux
SBC model |
echo $G_HW_MODEL_NAME
or (EG: RPi3) NanoPi R2S (aarch64)Power supply used | (EG: 5V 1A RAVpower) 5V 15W
SD card used | (EG: SanDisk ultra) Sandisk ultra 16GB
Additional Information (if applicable)
Software title | (EG: Nextcloud) apt
Was the software title installed freshly or updated/migrated? No, but worked until now on my customer's systems
Can this issue be replicated on a fresh installation of DietPi? I don't know, this is a production system distributed to many customers
Steps to reproduce
Open ssh
Enter:
# apt-get update
Result:
Expected behaviour
No error message
Actual behaviour
Error message see above. My distibuted client systems dan't be updated any more
Extra details
This seems to be an issue that more than once happed and was more than once fixed. I saw that in the net. But I have no idea to whom I can address this issue. The ambios in git has no issue tracker :-( Any ideas how you can help me so my customer's systems can be updated again? My update script catches this error on the remote systems and stops working so I have no chance to fix anything on the customer's systems out in the field :-( I guess it is a repository error but who is able to fix it???? At the moment this is a dead end street for me and I'm a little desperate.