Package Details: trustedqsl 2.8.1-2

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: LicenseRef-:ARRL
Conflicts: trustedqsl-git
Provides: tqsllib, trustedqsl
Replaces: tqsl
Submitter: jecxjo
Maintainer: not_anonymous
Last Packager: not_anonymous
Votes: 27
Popularity: 0.90
First Submitted: 2011-08-27 23:42 (UTC)
Last Updated: 2025-06-10 02:55 (UTC)

Latest Comments

1 2 3 4 5 6 .. 10 Next › Last »

not_anonymous commented on 2025-06-10 02:58 (UTC)

Updated !

ok1dtm commented on 2025-06-08 15:28 (UTC)

giovanni : Thank you very much for help. I changed in PKGBUILD in the depens section wxgtk3 for wxwidgets-gtk3 and trusteqsl works very well!

giovanni commented on 2025-06-08 14:13 (UTC) (edited on 2025-06-08 14:15 (UTC) by giovanni)

Either you wait for the trustedsql maintainer to update the PKGBUILD by replacing wxgtk3 with wxwidgets-gtk3 or you download the snapshot, replace in the depends wxgtk3 with wxwidgets-gtk3 and create your own package with makepkg.

ok1dtm commented on 2025-06-08 10:18 (UTC)

Thank you for the information. Now I have installed wxwidgets-gtk3 3.2.8.1-2 but installation of trustedqsl is still not possible again: -> "could not find all required packages: wxgtk3"

Some symlink wxwidgets-gtk3 to wxgtk?

giovanni commented on 2025-06-08 06:27 (UTC)

Please, replace wxgtk3 with wxwidgets-gtk3

ok1dtm commented on 2025-06-08 04:26 (UTC)

Cannot install trustedqsl 2.8.1-1 Error: -> could not find all required packages: wxgtk3 wxgtk3 is not in the repository Please how to proceed?

not_anonymous commented on 2024-11-09 18:38 (UTC) (edited on 2024-11-09 18:55 (UTC) by not_anonymous)

SOMEONE keeps flagging this out of date...please do NOT flag "out-of-date" unless it IS out of date !! The reason, I am told, is that the packages listed on the conflicts (et al) field(s) are not extent. Well, they were at one point, so they may be on someone's system; hence they should remain extent....FURTHER, the same person had asked that this package (and others) to be "orphaned" for the same reason. Thankfully the request was turned down. PLEASE, let's try to be kind to one another about such things.

not_anonymous commented on 2024-05-13 13:16 (UTC)

BUT...I went ahead and updated the package to conform to those who(m) argue, including the authors of the namcap-utility, that "custom: " in the license filed is incorrect (albeit the Package Guidelines specifically DO allow for such a declaration).....double sigh./

not_anonymous commented on 2024-05-13 12:44 (UTC) (edited on 2024-05-13 12:46 (UTC) by not_anonymous)

Coelacanthus: You have asked that this package be "Orphaned" because it does NOT conform to package guidlines.

IN FACT; This package DOES conform to the current Package Guidelines, and I quote:

"For custom licenses the identifier should be either LicenseRef-license-name or custom:license-name, if they are not covered by the common families mentioned above. The corresponding license text must be placed in directory /usr/share/licenses/pkgname. To install the file a following code snippet may be used in package() section:

install -Dm644 LICENSE "$pkgdir/usr/share/licenses/$pkgname/LICENSE" "

Coelacanthus commented on 2024-01-16 16:09 (UTC)

Please follow RFC16 use LicenseRef-ARRL

1 2 3 4 5 6 .. 10 Next › Last »