D-Star "jq" error in line 704 with V3.16

[kuhnje]

Nice addition with resolving class. Working here for DMR and P25. D-Star giving:

/use/local/bin/pistar-lastqso: line 704: jq: command not found

I'll have to try our Fusion also as have another running Fusion -> DMR crossover.

Thanks!

[kencormack]

It is odd that jq can not be found. Did you run the pistar-lastqso "install" script? That script, among other things, installs the jq command from the standard repositories. The jq binary ends up in /usr/bin, which is surely in the pi-star user's $PATH.

[kuhnje]

I think I'm on the way to fixing it. It's probably just on my end as jq isn't installed on my D-Star RPi. Working on that now..

Edit: ok, I manually installed "jq" using dpkg. It was on my end. It's working as should now.

[kencormack]

If you run my install script, it will install jq for you. Please read the following instructions that I provide in the README.
https://github.com/kencormack/pistar-lastqso#installation

[kencormack]

Oh, and yes. In the unix/linux world, the pipe symbol "|" normally signifies "or". Glad you caught that.

So, it sounds like there isn't really a problem with the script, but rather, that the install wasn't run, and that the pipe symbol was misunderstood. Let me know when you've run the install, and see what your results are, at that time.

[kuhnje]

I ran the install several times, but it wasn't installing jq. It wasn't a problem with the install script, but rather the repository list on that RPi somehow got messed up so it only tried to install jq with the install. Installed it manually by downloading the .deb and using dpkg to install it and it was fine. That RPi is running an old version of Pi-Star anyway, I'm going to update it sometime tomorrow. It's so old that it needs to be completely updated by installing from a new .img

They are all working fine now: DMR, P25, D-Star, and YSF. Thanks and Merry Christmas!

[kencormack]

I'm glad everything is working now, but keep in mind that pistar-lastqso began life when pi-star was version 4.1.4, and NO testing was ever done (nor will it be) on earlier versions. This is another point I will have to make, front and center, in the README.

[kencormack]

To clarify for our viewers at home who may be reading this thread...

First, there was initially some confusion over the syntax of the command line option.
Indeed, the pipe symbol is universally used in *nix documentation to represent an "or". The appropriate syntax of this option (as with all the others) is to use either -F (the short form) or --FCC (the long form).

" It’s is only under D-Star that I’m getting that "jq" error in line 704."
Though I was initially puzzled by the statement that the "not found" was happening opnly on D-Star, when the same function is called by multiple modes, it was revealed that the user has multiple hotspots, each configured for a different mode. The one running his D-Star config is running an older (unsupported) version of pi-star. His other hotspots were not having this problem.

That he was getting "command not found" on the one affected hotspot was due to the install script having difficulties installing the "jq" package from the repositories. He subsequently stated that he had been having problems with a corrupt apt database on that hotspot. Cleaning that up, and then manually installing the jq package, addressed the problem.

In summary, the issues were a misunderstanding of command line syntax, an outdated/unsupported version of pi-star, and a pre-existing problem with his apt database.

Ken