Package Details: trustedqsl 2.5.1-1

Git Clone URL: https://aur.archlinux.org/trustedqsl.git (read-only, click to copy)
Package Base: trustedqsl
Description: QSO log signing data for the ARRL Logbook of The World (LoTW)
Upstream URL: http://lotw.arrl.org/
Licenses: custom:ARRL
Conflicts: trustedqsl-git
Provides: tqsllib, trustedqsl
Replaces: tqsl
Submitter: jecxjo
Maintainer: not_anonymous
Last Packager: not_anonymous
Votes: 20
Popularity: 0.28
First Submitted: 2011-08-27 23:42
Last Updated: 2020-03-18 23:22

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

not_anonymous commented on 2017-05-25 15:22

Thanks for the report that wxgtk 3.x does not work at this time. I'm glad that this package is not using it.

I do not understand what a "regular repository" means v/v aur. There is only one aur and it is adjunct to other repositories like core, extra and community. IF something is not available outside of aur, then you will find it in aur (or not at all). SO...assuming your system is a.o.k. v/v setup; you should be able to type "yaourt trustedqsl" and yaourt should get stuff straightened out as needed.

I checked the dep. chain and ALL of the packages you had to install "manually" ARE in the aur OR the "binary repos" (core, base, or community) and *should-have* been installed as needed.

noway2 commented on 2017-05-24 20:06

The package seems to be linked against wxgtk2.8 though the current version in the regular repository is 3.0.3.1-1. I had great difficulty in getting trustedsql to obtain the dependencies and compile. It would not compile against version 3 despite the comment below to the effect that it would and instead would complain about missing some wx_widgets LIBRARIES. wxgtk2.8 has been moved to AUR and I was able to get that to compile after obtaining gstreamer0.10 and gstreamer0.10-base, both of which are older than the current repository versions. Getting these installed required a large number of dependencies that, thankfully were in the regular repository and these versions would compile against them. Attempts to have AUR, or yaourt, automatically obtain the required dependencies would fail claiming they could not be found requiring me to manually slog through them.

not_anonymous commented on 2017-05-12 02:58

It's there.....try running this from a command prompt: pacman -Qo /usr/bin/tqsl

martinm1000 commented on 2017-05-12 02:06

I did install it, /usr/lib/trustedqsl/libtqsllib.so is there, but no /usr/bin/tsql ?

First time installing that package/software ! - 73

Edit: All right, I found it in the menus. Still don't get why the bin/ file indicated in the details wasn't put there...

not_anonymous commented on 2017-04-27 20:21

Updated !! (Tnxs OM for the comment and tnxs to the ARRL for pushing 2.3.1 out.)

tmdavis3 commented on 2017-04-27 03:32

I had no problems with the dependencies compiling.
The build passed the checks, but still failed. It seems to be something broken between openssl and trustedqsl. I did not build openssl. It was pulled in as a package, version 1.1.0e.

You can view the build attempt logs here:
https://pastebin.com/1W0s7WKw

not_anonymous commented on 2017-02-08 22:12

wxgtk2.8 does compile now....
*** I will look into changing this with the next release.
chuser: Please note that trustedqsl-git is *strongly* recommended until (at least) the next release of trustedqsl, as there are some *known* problems with version 2.3 actually working correctly (on linux machines) !!

chuser commented on 2017-02-03 17:51

wxgtk2.8 won't build any longer (for me, at least), but per the TQSL ChangeLog it built OK against wxgtk 3.0.x

not_anonymous commented on 2017-01-22 18:22

I went ahead and updated this to version 2.3 ALTHOUGH it still has the bugs. (I fixed a number of packaging issues.) ***If you want something that works well, (i.e. as in no obvious bugs) please use the "trustedqsl-git" package.

not_anonymous commented on 2016-11-14 16:00

Checked the changelog at the sourceforge website. The *latest* version, 2.3 has a number of bugs that are being/have been corrected. I am electing to hold the version for a bit longer. You can, of course, update the version number to 2.3 (and the checksums), and proceed.

For more info on what will become 2.3.1; Go here:
< https://sourceforge.net/p/trustedqsl/tqsl/ci/460d71a2f5c66350d6843dcaade473d093170af7/log/?path= >