Does anyone know anything about the APT key not being generated after using satnogs-setup?

For context, I just put the legacy version image from the wiki on a raspberry pi 4 that I’m working with now, and I was following the setup instructions on the wiki page. I did the standard sudo apt update and sudo apt upgrade before using the satnogs setup. I did have the ground station up on the satnogs network with the new client but figured out that it doesn’t support serial. I copied over the settings on the working ground station, but it keeps giving me this error:

Executing playbook local.yml

  • localhost on hosts: localhost -
    Gathering Facts…
    Check Ansible version…
    Check distribution…
    Remove APT configuration disabling recommends…
    Update APT cache…
    Install required package for APT…
    Install repository keys…
    Retrying… (1 of 4)
    Retrying… (2 of 4)
    Retrying… (3 of 4)
    localhost failed | msg: apt-key did not return an error, but failed to add the key (check that the id is correct and not a subkey)

  • Play recap -
    localhost : ok=6 changed=0 unreachable=0 failed=1 rescued=0 ignored=0

If there is any information on how to get around this APT key problem, information would be much appreciated.

wget http://download.opensuse.org/repositories/home:/librespace:/satnogs/Raspbian_11/Release.key -O satnogs-release.key
sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/satnogs.gpg satnogs-release.key

I still get the same error.

The various keys in OBS are being rebuilt, but it has taken more than a week now and it’s still not done on all arches. No clue when it’ll be done.

What does this mean for the legacy satnogs-setup? Are all stations using this legacy not currently able to work?

As far as I know, this is only affecting new installation attempts. I know people who are using the legacy setup who set theirs up about a year ago, and they have not gone offline yet.

1 Like

No, the legacy stations are still working.

The problem arises when a fresh installation or an update of the current one needs to be performed, the packages can no longer be installed or upgraded.

@Acinonyx any additional information on the legacy stations ?

Jan | PE0SAT

1 Like

Still not working, cannot update my non docker stations

Install repository keys…
Retrying… (1 of 4)
Retrying… (2 of 4)
Retrying… (3 of 4)
localhost failed | msg: apt-key did not return an error, but failed to add the key (check that the id is correct and not a subkey)

Apart from the SatNOGS update function.

What do you get when running sudo apt-get update on the cli?

Jan | PE0SAT

pi@raspberrypi:~ $ sudo apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:3 http://download.opensuse.org/repositories/home:/librespace:/satnogs/Raspbian_11 ./ InRelease
Hit:4 http://ppa.launchpad.net/ansible/ansible/ubuntu focal InRelease
Reading package lists... Done
pi@raspberrypi:~ $ sudo apt update
Hit:1 http://ppa.launchpad.net/ansible/ansible/ubuntu focal InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:4 http://download.opensuse.org/repositories/home:/librespace:/satnogs/Raspbian_11 ./ InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
1 Like

Weird, here there is no key error/warning although it is using the same keys as ansible.

I guess we are at a point that “old” legacy systems are no longer supported and we can only update and configure them manually.

It would be great if there was an “official” statement on the releases and if they are still supported.

Jan | PE0SAT

And it’s not that I need to update because of missing feautures, my station 3442 appears to be mis-fitting scheduled observations so all fail (as shown in different topic)

Can you point me to instructions for manual update or should I start from scratch and re-use station name and settings ?