Yeah, it does work, but only stable. In fact, we test Ansible on Debian Buster before flashing and final testing to RPi because it is faster.
Only stable branch is currently stable (what a surprise!). master branch is in a broken state until flowgraphs are compiled into a package. Flowgraphs have recently been moved into a new repository and will be maintained and packaged separately from gr-satnogs which makes SCM and contributions much more clean and flexible.
Agreed, the package gr-satnogs 2.0-1 seems broken to me when installed on a fresh pre-built Pi3 image previously updated with satnogs-setup (experiemental=True) to the latest master.
The installation of gr-satnogs 2.0-1 and libgnuradio-satnogs 2.0-1 was performed manually with
This bug was fixed in gr-satnogs@0ba9e0e, so gr-satnogs master is fixed.
According to this the stable branch seems broken to me currently due to the potentially broken gr-satnogs 2.0-1 release and the unstable branch/experimental=True is missing the satnogs-flowgraphs package. The latter can be fixed by a manual installation of satnogs-flowgraphs.
Note that on a station following the stable branch of satnogs-client-ansible gr-satnogs will be installed in version 1.5.1-1 (see stable@satnogs-client-ansible:/satnogs-radio/defaults/main.yml), so the conclusion that the stable branch is broken in my previous post was wrong.
My problem with gr-satnogs 2.0-1 was caused by having installed an incompatible (too new) version of gr-soapy (ec2eb8e@gr-soapy instead of the required gr-soapy 2.0) due to a breaking change in the upcoming unreleased version of gr-soapy.
Since ~ 2020-02-08 the stable repositories (home:librespace:satnogs) contain a gnuradio package 3.8.0.0-6, so this gets installed instead of gnuradio 3.7 provided by debian 10/buster (and required by gr-satnogs 1.5.1). This could be the reason why stable might be broken (I didn’t try to reproduce myself).
If this is the case, apt-pinning gnuradio to 3.7.* should solve the issue. Add the following to /etc/apt/preferences.d/satnogs (untested):
Package: gnuradio
Pin: version 3.7.*
Pin-Priority: 1001
I pinned gnuradio so the issue should be fixed now. Only new installations should have been affected or installations where a manual update was performed. Updates through satnogs-setup should not have been affected since apt dist-upgrade does not resolve package conflicts automatically.
satnogs-setups -
Gathering Facts…
[WARNING]: Failure using method (v2_runner_on_unreachable) in callback plugin
(<ansible.plugins.callback.unixy.CallbackModule object at 0xb52c6eb0>):
‘CallbackModule’ object has no attribute ‘delegated_vars’
to retry, use: --limit @/home/pi/satnogs-client-ansible/site.retry
Play recap -
satnogs : ok=0 changed=0 unreachable=1 failed=0