Kernel version | Linux loxberry 6.6.62+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.62-1+rpt1 (2024-11-25) aarch64 GNU/Linux
Architecture | arm64
Hardware model | RPi 5 Model B (aarch64) (ID=5)
Power supply | (EG: RAVPower 5V 1A)
SD card | (EG: SanDisk Ultra 16 GB)
Steps to reproduce:
…
…
Expected behaviour:
…
Actual behaviour:
…
Extra details:
…
Additional logs:
Ign:1 https://repo.ebusd.eu/apt/default/bookworm bookworm InRelease
Get:2 https://packages.sury.org/php bookworm InRelease [6136 B]
Hit:3 https://deb.debian.org/debian bookworm InRelease
Hit:4 https://deb.debian.org/debian bookworm-updates InRelease
Get:5 https://dl.yarnpkg.com/debian stable InRelease
Hit:6 https://deb.debian.org/debian-security bookworm-security InRelease
Hit:7 https://deb.debian.org/debian bookworm-backports InRelease
Hit:8 https://dietpi.com/apt bookworm InRelease
Err:2 https://packages.sury.org/php bookworm InRelease
The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <deb@sury.org>
Hit:9 https://dietpi.com/apt all InRelease
Hit:10 https://archive.raspberrypi.com/debian bookworm InRelease
Hit:11 https://pkg.cloudflare.com/cloudflared any InRelease
Err:5 https://dl.yarnpkg.com/debian stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525
Ign:1 https://repo.ebusd.eu/apt/default/bookworm bookworm InRelease
Ign:1 https://repo.ebusd.eu/apt/default/bookworm bookworm InRelease
Err:1 https://repo.ebusd.eu/apt/default/bookworm bookworm InRelease
Something wicked happened resolving 'repo.ebusd.eu:https' (-5 - No address associated with hostname)
Fetched 22.7 kB in 7s (3207 B/s)
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://pack ages.sury.org/php bookworm InRelease: The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <deb@sury.org >
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.y arnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525
E: Failed to fetch https://repo.ebusd.eu/apt/default/bookworm/dists/bookworm/InRelease Something wicked happened resolving 'repo.ebusd.eu:https' (-5 - No address associated with hostname)
E: Failed to fetch https://packages.sury.org/php/dists/bookworm/InRelease The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.OR G Automatic Signing Key <deb@sury.org>
E: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures couldn't be verified because the public key is not ava ilable: NO_PUBKEY 62D54FD4003F6525
E: Some index files failed to download. They have been ignored, or old ones used instead.
Thanks for the fast response. I will talk to the Loxberry devs. If I can’t get the update to work are there any security relevant changes from my version to the newest one or could I still live with my current version if the upgrade issue can’t be solved?
You should definitely solve those issues ASAP, as with such an old package state, your system is at high risk, and possibly a risk for other systems across the Internet, as part of a botnet or similar. APT upgrades should be done at a weekly, better daily basis, especially in times of AI tools being able to find and exploit security vulnerabilities within hours.
If you did not add those 3 APT repositories by yourself, then yes, at best talk to Loxberry whether they were added their end, and how to update the keys, and what to replace repo.ebusd.eu with (which does not exist anymore).
If you did add those repos by yourself, then check back whether your really still need those, and for what:
yarn is a Node.js package/dependency manager, which can be installed via npm and alike directly. It is uncommon to install it via APT repository.
The PHP repository is reasonable only if you require a specific different PHP version on your Debian version. But using it has some risks, since it ships a bunch of other system libraries, which can cause incompatibilities. Usually I’d recommend to stick with the native Debian PHP packages, upgrade Debian itself if you need a newer PHP version, and stop using software which requires older PHP to run (as this means it is badly maintained, and possibly a security issue by itself).
I didn’t added any of these packages myself I already reached out to the Loxberry developers. Assuming they cannot help what are my best options?
Regarding repo.ebusd.eu: I guess this repo is for the ebusd-plugin in loxberry. The big advantage is it has a GUI where you can check the ebus values directly. But if that’s the issue I guess I have to just delete the repo?