pi@sadie:~ $ curl https://blokas.io/pisound/install.sh | sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2438 100 2438 0 0 4945 0 --:--:-- --:--:-- --:--:-- 4945
Checking if the kernel version is or newer... It is.
Importing Blokas GPG public key...
dd: failed to open '/etc/apt/keyrings/blokas-archive-keyring.gpg': No such file or directory
(23) Failed writing body
Adding Blokas APT rpi repository...
Updating package list...
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease------
Get:3 http://apt.blokas.io rpi InRelease [3,954 B]------------------
Err:3 http://apt.blokas.io rpi InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 37808098F560908A
Reading package lists... Done
W: GPG error: http://apt.blokas.io rpi InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 37808098F560908A
E: The repository 'http://apt.blokas.io rpi InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Installing Pisound software...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package pisound
Updating /usr/local/pisound...
sh: 1: cd: can't cd to /usr/local/pisound
Now you may run 'sudo pisound-config' to customize your installation!
Is this a Bullseye problem or an apt.blokas.io issue with the GPG key?
Thanks!!!