Re: wsjtx

[Greg Beam <ki7mt@yahoo.com>]

Hi Ian,

See comments below.

On 10/18/2015 16:16, Iain R. Learmonth wrote:
> Hi,
>
> I've been trying to use the wsjtx as currently packaged in Debian. It
> appears to segfault every time it comes round to transmitting, which is not
> brilliantly useful.

Build it and enable the Debug options, then run it with GDB.

I've tested v1.5.0, 1.6.0 adn v1.6.1, and have yet to get a Segfault. 
Can you detail exactly how you installed and run v1.5.0?

> I took a go at attempting to update the package in Debian to the latest
> upstream version (1.5.0) from the website. After 8 hours, I'm giving up.

It can't be done with the current Upstream package setup. but that's 
change in the not to distant future.

> This is not a friendly package for distributions to carry, it combines 3
> build systems together making it incredibly difficult to see when your
> options are overwritten and if they are, where it is happening.

With the current packaging method, "It Can't" be carried by Debian, as 
it's using a Custom Static version of Hamlib. This issue will be 
resolved in the not to distant future.

Additionally, KVASD ( the non-FOSS decoder) is about to be replaced by a 
complete Open Source Decoder, with equal performance.

> I will look at reproducing this bug later in the week and I will be filing
> an RC bug on the package if I can reproduce it reliably. I see that 1.5.0 is
> packaged in KI7MT's Ubuntu PPA, although the package would not be acceptable
> for the Debian archives.

As everyone knows, Launchpad is not for Debian, I get reminded of this 
all the time when I even mention word "Launchpad" in Debian arenas. I 
can say, for certain, there's not problems with 1.5.0, 1.6.0 or 1.6.1 
branches on Ubuntu Trusty, Vivid or Wily. And, I don't recall any faults 
of the three branches on Jessie, for what it's worth.

> Could someone provide a status update as to where these packages are in
> their development? If no one is interested in the package any more, please
> orphan it, although know that if that happens there's a good chance I'll
> follow up with an RM bug.

A Couple of things to note:

[1] I've not looked recently, but I believe Nate (the Hamlib developer) 
release version 3.0 or there about. At some point, WSJT-X will start to 
use the distribution of Hamlib rather than a customer static library. 
There's no sense in trying to package this any further until that happens.

[2] WSJT-X still relies on KVASD, the non-FOSS decoder, however, the 
upstream team is about to release a FOSS decoder that is equal too or 
better than KVASD, so, again, no point in pressing ahead until this 
happens as WSJT-X, without the KVASD binary is severely degraded. 
However, you can use the utility package ( PPA: kvasd-installer ) to 
install  the decoder after installing WSJT-X.

> You can see my attempt at bringing this to the latest upstream version at:
>
>    http://anonscm.debian.org/cgit/pkg-hamradio/wsjtx.git

I'll have a look at the info and see if there is anything obvious I can 
detect.

> Thanks,
> Iain.

73's
Greg, KI7MT