Err:5 https://repo.z-wave.me/z-way/raspbian buster InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D5AA8FC24C6547A2
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.z-wave.me/z-way/raspbian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D5AA8FC24C6547A2
W: Failed to fetch https://repo.z-wave.me/z-way/raspbian/dists/buster/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D5AA8FC24C6547A2
Yes, the old key has expired and the new one is available from the key server. You can use the following script to update it: https://storage.z-wave.me/RaspbianInstall (this is the script you used to download Z-Way)
Yes, the old key has expired and the new one is available from the key server. You can use the following script to update it: https://storage.z-wave.me/RaspbianInstall (this is the script you used to download Z-Way)
Is there a reason why https://repo.z-wave.me/z-way/raspbian/p ... _armhf.deb apparently got at least touched along the way? It has a timestamp of July 20th but it has been released for quite a while longer now. (I do not have saved the old .deb so I can cmp its contents.) A simple key exchange should not have affected the pool contents. Sorry for being paranoid, and I know no serious hacker would leave a silly timestamp like this, but I really think you should be extra transparent with all of your activities these days.
Raspberry Pi 3 Model B Rev 1.2
Raspbian GNU/Linux 10 (buster)
RaZberry ZW0500 1024/2 SDK: 6.82.01 API: 05.39
Z-Way version v4.1.0
We have re-uploaded all .deb packages with fixed dependencies. The code was not re-compiled, just .deb dependency altered. All this to allow arm 64 installations. Soon we will release the new script that will allow both arm 32 and 64 bits installations.
