Bug#999470: wsjtx: Stable backport wsjt-x 2.5.2

[Christoph Berg <myon@debian.org>]

Re: tony mancill
> > So the wsjtx backport is likely just wsjtx, without hamlib. Testing
> > that just requires starting it up and checking if it can talk to your
> > TRX properly.
> 
> Building against hamlib 4.0 (clean bullseye chroot) fails with errors
> like this:
> 
> /<<PKGBUILDDIR>>/Transceiver/HamlibTransceiver.cpp:60:66: error: ‘RIG_CAPS_MFG_NAME_CPTR’ was not declared in this scope
>    60 |         key = QString::fromLatin1 (rig_get_caps_cptr (rig_model, RIG_CAPS_MFG_NAME_CPTR)).trimmed ()
>       |                                                                  ^~~~~~~~~~~~~~~~~~~~~~
> 
> There are 51 errors in total.

Oh ok, then they have moved on to requiring the newer versions.

> > Hamlib doesn't seem as compatible as the no-soname-change suggests, I
> > also had to recompile fldigi to have it work with Hamlib 4.3 here (at
> > least via rigctld).
> 
> In that case, it sounds like the next step is try to backport to wsjtx
> 2.5.x to hamlib 4.0.

Hmm. It might be worth a shot since backporting the new hamlib will
probably break other things.

I'm unsure if backporting hamlib is something we should do - possibly
telling people to upgrade their shack to testing results in less
friction.

Christoph