Re: Bug#906899: wsjtx: Upstream 1.9.1 available
Howdy all,
I started work on the wsjt-x 1.8.0 release and got it into a working state - that's what is currently on Salsa. Sadly I never had the time to do testing/etc, and life has been in the way since.
When I was working on packaging it, I came across a few issues and made a few decisions that are worth nothing going forward into 1.9.1 -
* I removed the version of hamlib supplied with the package and retarred it, hence the +repack tag. If there's a more sensible way to do this, I'm keen to see it!
* Given the size of the examples and document package relative to the actual binaries, I split those into their own package with an architecture of -all. This would need to go through NEW as it's a new package, but it keeps lintian happy!
* WSJT-X ships with a number of new, undocumented calibration/testing/development binaries to assist in debugging/developing things, as far as I can see. I removed a number of these, as I don't know enough about them and the functionality was sufficiently minimal that writing a man page seemed over the top.
Also:
* It builds with debian provided libraries
* I added the required rules for hardening the binaries
* irl ensured it built with QT5, I think...
Hopefully pulling in new upstream shouldn't break everything and it should continue to build as is, after a repack...
I can add this to my to-do list tomorrow afternoon, or someone else more knowledgable can do it!
Cheers,
DH
--
Hibby
d@vehibberd.com
MM3ZRZ
On Thu, 23 Aug 2018, at 6:15 PM, Ervin Hegedüs wrote:
> Hi all,
>
> On Thu, Aug 23, 2018 at 05:47:25PM +0200, Enrico Rossi wrote:
> > Hi,
> >
> > could I suggest we continue this discussion on the mailing list?
>
> sure - this is my last e-mail on this thread, removed the #906899
> address, and added the debian-hams.
>
> Reference is here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906899
>
> > Anyway the target would be to have wsjtx 1.8 working with hamlib 3.2
> > provided by Debian and (hopefully) libboost provided by Debian.
>
> of course, my package works only with Debian packages, incl.
> Hamlib...
>
> > Wsjtx 1.9.1 brings his own hamlib, which it looks like this hamlib
> > commit d1b545b 2018-05-25.
>
> (perhaps) all WSJT-X could work with external Hamlib. I checked
> it first at 1.8, that worked.
>
> > Three days ago hamlib 3.3 has been committed, so it is reasonable to
> > think to have a wsjtx builded on top of hamlib 3.3 provided by Debian
> > and the same for libboost.
>
> I have to see my subscription status of Hamlib list... few
> months ago didn't arrives any mail...
>
> > I think this is a reasonable plan.
>
> sounds good,
>
>
> 73, Ervin
>
Reply to: