You can subscribe to this list here.
2013 |
Jan
|
Feb
|
Mar
(221) |
Apr
(14) |
May
(49) |
Jun
(9) |
Jul
(51) |
Aug
(15) |
Sep
(28) |
Oct
(2) |
Nov
(10) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2014 |
Jan
(49) |
Feb
(8) |
Mar
(10) |
Apr
(7) |
May
(1) |
Jun
(2) |
Jul
(9) |
Aug
|
Sep
|
Oct
(4) |
Nov
(4) |
Dec
(1) |
2015 |
Jan
(8) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(8) |
Sep
(1) |
Oct
|
Nov
|
Dec
(8) |
2016 |
Jan
|
Feb
(10) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
(8) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
(5) |
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
(17) |
Dec
(11) |
2019 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2020 |
Jan
|
Feb
(15) |
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(6) |
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(3) |
Dec
(16) |
2022 |
Jan
|
Feb
(6) |
Mar
(6) |
Apr
|
May
(2) |
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(13) |
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Greg T. <gd...@le...> - 2021-09-18 15:23:22
|
https://www.rickmurphy.net/lotw/tqsl-2.5.9.tar.gz (Linux/BSD) This is the expected source tarball and that's I tested. I locally updated the pkgsrc package to 2.5.9 and it builds ok on NetBSD 9 amd64, and starts up. While cleaning up our patches, I noticed that there we added a NetBSD-specific include to get PATH_MAX defined, which made me notice two things: There's a TQSL_MAX_PATH_LEN set to 256, and I'm not sure why this isn't system PATH_MAX. But I think PATH_MAX has to be >=1024, so this merely results in some crayz long but technically legal paths not being ok, and that seems highly unlikely to bother people. In openssl_cert.cpp, there are ifdefs to define PATH_MAX if undefined, at line 3124. This seems slightly dangerous because POSIX more or less requires PATH_MAX and thus I think it's best to ifdef remediation for that on systems that are known to need it. And, I don't see an include of <limits.h>, which is what POSIX says one needs to get PATH_MAX defined. However the actual spec is messy, and there's a notion that code might just rely on the minimum value. But, I think code that uses PATH_MAX should include limits.h. At the moment this problem seems theoretical. https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html And this is of course a small list of small nits, which is a great testing report... 73 de n1dam |
From: Rick M. <k1m...@gm...> - 2021-09-18 02:30:26
|
There's a few long-standing defects in TQSL that this release is intended to correct. 1. TQSL did not recognize the 'S' type-specifier in an ADIF tag. It expected the ADIF 1.0 'C' specifier for strings, and when presented with a valid ADIF file containing a 'S' would generate a spurious error (but would properly sign the log.) TQSL now accepts both 'S' (String) and 'C' (Character) specifiers. 2. For AMSAT-Oscar 7, TQSL now accepts "AO-07" as well as "AO-7" for the satellite name. 3. ADIF mode mapping for modes containing slashes (such as "HELL/150") would not work due to a parsing error. You could enter a mode mapping, which would be ignored. ADIF Modes with slashes can now be mapped to an existing mode (such as "DATA"). 4. Remove forced background color settings so system settings for "Dark Mode" work. (Linux only.) 5. Correct the languages "Chinese Traditional" and "Chinese Simplified" as they were reversed. Usual download locations: https://www.rickmurphy.net/lotw/tqsl-2.5.9.msi (Windows) https://www.rickmurphy.net/lotw/tqsl-2.5.9.pkg (Mac, 64-bit) https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.9.pkg (Mac, 32-bit/PPC) https://www.rickmurphy.net/lotw/tqsl-2.5.9.tar.gz (Linux/BSD) Any feedback for this release is greatly appreciated. 73, -Rick -- Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1...@ar...> - 2021-05-11 23:00:16
|
I've published the 2.5.8 beta. Changes in this release: 1. New Chinese (Simplified) translation by 2. When configuring a station location where only one CQ zone or only one ITU zone applies, then this value is forced. 3. Display of the last usable date of a callsign certificate now shows the date of the last QSO that can be signed. 4. The format of IOTA entries is now checked for validity. 5. When a station location is added or edited, an automatic backup is triggered. 6. TQSL now accepts "AO-07" for satellite "AO-7". 7. Correct handling of the Russian Oblast "YN" - Logbook coded this as "JN" incorrectly. Please download and give this release a try. I would greatly appreciate any feedback. Windows: https://www.rickmurphy.net/lotw/tqsl-2.5.8.msi Mac: https://www.rickmurphy.net/lotw/tqsl-2.5.8.pkg (64-bit) https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.8.pkg (32-bit) Unix: https://www.rickmurphy.net/lotw/tqsl-2.5.8.tar.gz 73, -Rick -- Rick Murphy, D.Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1...@ar...> - 2020-11-02 00:01:56
|
Walter, Makes sense - there's probably some change in 3.1.4 that keeps this from building, but it's good to catch this before it's released. 73, -Rick On Sun, Nov 1, 2020 at 3:49 PM Walter Fey <dl...@da...> wrote: > This patch fixes the build problem on all current openSUSE versions. > > Default wxWidgets version of Leap 15.1 and 15.2 is 3.0.3 , Tumbleweed has > 3.1.4 > > Thank you for the fix. > > 73, Walter DL8FCL > > > Am 01.11.20 um 18:07 schrieb Rick Murphy: > > This is an issue where TQSL is depending on an implicit conversion to wide > characters that your system isn't allowing. Relying on implicit conversions > can cause problems like this. > > I've checked in a correction to the repository. Patch to correct this is > below. > > Thanks for reporting this. It wasn't at all what I thought. > 73, > -Rick > > diff --git a/apps/tqsl.cpp b/apps/tqsl.cpp > index 1e9075c..f7a5d7d 100644 > --- a/apps/tqsl.cpp > +++ b/apps/tqsl.cpp > @@ -745,7 +745,7 @@ class LogList : public wxLog { > > #if wxMAJOR_VERSION > 2 > void LogList::DoLogText(const wxString& msg) { > - const wxChar* szString(msg); > + const wxChar* szString = msg.wc_str(); > #else > void LogList::DoLogString(const wxChar *szString, time_t) { > static wxString msg(szString); > @@ -789,7 +789,7 @@ class LogStderr : public wxLog { > > #if wxMAJOR_VERSION > 2 > void LogStderr::DoLogText(const wxString& msg) { > - const wxChar* szString(msg); > + const wxChar* szString = msg.wc_str(); > #else > void LogStderr::DoLogString(const wxChar *szString, time_t) { > static wxString msg(szString); > @@ -5452,11 +5452,11 @@ QSLApp::OnInit() { > wxString av = argv[0]; > myArgv[0] = strdup(av.ToUTF8()); > #else > - myArgv[0] = strdup(argv[0]); > + myArgv[0] = strdup(argv[0].ToUTF8()); > #endif > myArgc = 1; > for (int i = 1; i < argc; i++) { > - if ((const wxChar *)argv[i]) { > + if ((const wxChar *)argv[i].mb_str().data()) { > if ((i + 1) < argc) { > wxString av1 = argv[i+1]; > #if wxMAJOR_VERSION == 2 > @@ -5471,9 +5471,9 @@ QSLApp::OnInit() { > } > origCommandLine += wxT(" "); > #if wxMAJOR_VERSION == 2 > - myArgv[myArgc] = > strdup(wxString(argv[i]).ToUTF8());; > + myArgv[myArgc] = > strdup(wxString(argv[i]).ToUTF8()); > #else > - myArgv[myArgc] = strdup(argv[i]); > + myArgv[myArgc] = strdup(argv[i].ToUTF8()); > #endif > #ifdef _WIN32 > if (myArgv[myArgc][0] == '-' || myArgv[myArgc][0] > == '/') > > On Sun, Nov 1, 2020 at 8:07 AM Rick Murphy <k1...@ar...> wrote: > >> I've reproduced this on an older version of openSUSE that I had a VM for >> already. >> Are you building against wxWidgets 2.x? Do you have 3.x libraries >> available? 2.x is going to be end-of-life soon if not already - 2.8.12, >> the latest 2.x release, came out in 2011. >> 73, >> -Rick >> >> On Sat, Oct 31, 2020 at 11:06 PM Rick Murphy <k1...@ar...> wrote: >> >>> What is your suggested fix? openSUSE has this problem for multiple >>> wxWidgets consumers. For example, from 2016: >>> https://forum.audacityteam.org/viewtopic.php?t=89971&start=10 >>> >>> I'll be happy to upstream a fix, but this seems to be a deliberate >>> choice by openSuSE that leads to compatibility issues. >>> 73, >>> -Rick >>> >>> >>> >>> On Sat, Oct 31, 2020 at 10:47 PM Walter Fey <dl...@da...> wrote: >>> >>>> Compilation for openSUSE 15.2 and Tumbleweed fails. >>>> The build logs with the error at the end are added to this mail. >>>> >>>> 73, >>>> Walter DL8FCL >>>> >>>> >>>> Am 31.10.20 um 19:06 schrieb Rick Murphy: >>>> >>>> I've published a release candidate for TQSL 2.5.6 - details below. >>>> >>>> Defects Corrected: >>>> 1. In cases where applications pass empty passwords on the command line >>>> (-p ""), TQSL could ignore that password and handle the command >>>> incorrectly. This was not the behavior prior to TQSL 2.5.5. >>>> 2. Ask the user to save a log being edited in the ADIF editor when they >>>> close the editor window. Previously, TQSL would discard the file. >>>> 3. TQSL more accurately prints the line number of an ADIF file with an >>>> error message. In the past, TQSL always reported the line containing the >>>> end-of-record tag. >>>> >>>> In addition, TQSL now uses the word "Passphrase" to distinguish between >>>> the password used for the LoTW site and the passphrase used to secure a >>>> Callsign Certificate. >>>> >>>> TQSL now also has a Swedish localization, thanks to SM0LTV. The other >>>> localizations have also been updated. >>>> >>>> A big change in the packaging for TQSL 2.5.6 for MacOS is the use of a >>>> signed and notarized (by Apple) package file ".pkg" for installing TQSL on >>>> a Mac. Having a signed installer increases the compatibility with current >>>> MacOS versions (Catalina and Big Sur). I'm very interested in feedback with >>>> these package files, as they're much easier to install. >>>> >>>> Download links below. >>>> Windows: >>>> https://www.rickmurphy.net/lotw/tqsl-2.5.6.msi >>>> >>>> Mac (64/32 bit, current systems) >>>> https://www.rickmurphy.net/lotw/tqsl-2.5.6.pkg (Installer) >>>> https://www.rickmurphy.net/lotw/tqsl-2.5.6.dmg (Disk image) >>>> >>>> Mac (Intel 386/Power PC legacy systems) >>>> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.pkg (Installer) >>>> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.dmg (Disk image) >>>> >>>> Linux/BSD: >>>> https://www.rickmurphy.net/lotw/tqsl-2.5.6.tar.gz (source code only) >>>> 73, >>>> -Rick >>>> -- >>>> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >>>> >>>> >>>> _______________________________________________ >>>> Trustedqsl-testing mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing >>>> >>>> _______________________________________________ >>>> Trustedqsl-testing mailing list >>>> Tru...@li... >>>> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing >>>> >>> >>> >>> -- >>> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >>> >> >> >> -- >> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >> > > > -- > Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA > > > _______________________________________________ > Trustedqsl-testing mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing > > _______________________________________________ > Trustedqsl-testing mailing list > Tru...@li... > https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing > -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Walter F. <dl...@da...> - 2020-11-01 20:49:50
|
This patch fixes the build problem on all current openSUSE versions. Default wxWidgets version of Leap 15.1 and 15.2 is 3.0.3 , Tumbleweed has 3.1.4 Thank you for the fix. 73, Walter DL8FCL Am 01.11.20 um 18:07 schrieb Rick Murphy: > This is an issue where TQSL is depending on an implicit conversion to > wide characters that your system isn't allowing. Relying on implicit > conversions can cause problems like this. > > I've checked in a correction to the repository. Patch to correct this > is below. > > Thanks for reporting this. It wasn't at all what I thought. > 73, > -Rick > > diff --git a/apps/tqsl.cpp b/apps/tqsl.cpp > index 1e9075c..f7a5d7d 100644 > --- a/apps/tqsl.cpp > +++ b/apps/tqsl.cpp > @@ -745,7 +745,7 @@ class LogList : public wxLog { > > #if wxMAJOR_VERSION > 2 > void LogList::DoLogText(const wxString& msg) { > - const wxChar* szString(msg); > + const wxChar* szString = msg.wc_str(); > #else > void LogList::DoLogString(const wxChar *szString, time_t) { > static wxString msg(szString); > @@ -789,7 +789,7 @@ class LogStderr : public wxLog { > > #if wxMAJOR_VERSION > 2 > void LogStderr::DoLogText(const wxString& msg) { > - const wxChar* szString(msg); > + const wxChar* szString = msg.wc_str(); > #else > void LogStderr::DoLogString(const wxChar *szString, time_t) { > static wxString msg(szString); > @@ -5452,11 +5452,11 @@ QSLApp::OnInit() { > wxString av = argv[0]; > myArgv[0] = strdup(av.ToUTF8()); > #else > - myArgv[0] = strdup(argv[0]); > + myArgv[0] = strdup(argv[0].ToUTF8()); > #endif > myArgc = 1; > for (int i = 1; i < argc; i++) { > - if ((const wxChar *)argv[i]) { > + if ((const wxChar *)argv[i].mb_str().data()) { > if ((i + 1) < argc) { > wxString av1 = argv[i+1]; > #if wxMAJOR_VERSION == 2 > @@ -5471,9 +5471,9 @@ QSLApp::OnInit() { > } > origCommandLine += wxT(" "); > #if wxMAJOR_VERSION == 2 > - myArgv[myArgc] = > strdup(wxString(argv[i]).ToUTF8());; > + myArgv[myArgc] = > strdup(wxString(argv[i]).ToUTF8()); > #else > - myArgv[myArgc] = strdup(argv[i]); > + myArgv[myArgc] = strdup(argv[i].ToUTF8()); > #endif > #ifdef _WIN32 > if (myArgv[myArgc][0] == '-' || > myArgv[myArgc][0] == '/') > > On Sun, Nov 1, 2020 at 8:07 AM Rick Murphy <k1...@ar... > <mailto:k1...@ar...>> wrote: > > I've reproduced this on an older version of openSUSE that I had a > VM for already. > Are you building against wxWidgets 2.x? Do you have 3.x libraries > available? 2.x is going to be end-of-life soon if not already - > 2.8.12, the latest 2.x release, came out in 2011. > 73, > -Rick > > On Sat, Oct 31, 2020 at 11:06 PM Rick Murphy <k1...@ar... > <mailto:k1...@ar...>> wrote: > > What is your suggested fix? openSUSE has this problem for > multiple wxWidgets consumers. For example, from 2016: > https://forum.audacityteam.org/viewtopic.php?t=89971&start=10 > <https://forum.audacityteam.org/viewtopic.php?t=89971&start=10> > > I'll be happy to upstream a fix, but this seems to be a > deliberate choice by openSuSE that leads to compatibility issues. > 73, > -Rick > > > > On Sat, Oct 31, 2020 at 10:47 PM Walter Fey <dl...@da... > <mailto:dl...@da...>> wrote: > > Compilation for openSUSE 15.2 and Tumbleweed fails. > The build logs with the error at the end are added to this > mail. > > 73, > Walter DL8FCL > > > Am 31.10.20 um 19:06 schrieb Rick Murphy: >> I've published a release candidate for TQSL 2.5.6 - >> details below. >> >> Defects Corrected: >> 1. In cases where applications pass empty passwords on >> the command line (-p ""), TQSL could ignore that password >> and handle the command incorrectly. This was not the >> behavior prior to TQSL 2.5.5. >> 2. Ask the user to save a log being edited in the ADIF >> editor when they close the editor window. Previously, >> TQSL would discard the file. >> 3. TQSL more accurately prints the line number of an ADIF >> file with an error message. In the past, TQSL always >> reported the line containing the end-of-record tag. >> >> In addition, TQSL now uses the word "Passphrase" to >> distinguish between the password used for the LoTW site >> and the passphrase used to secure a Callsign Certificate. >> >> TQSL now also has a Swedish localization, thanks to >> SM0LTV. The other localizations have also been updated. >> >> A big change in the packaging for TQSL 2.5.6 for MacOS is >> the use of a signed and notarized (by Apple) package file >> ".pkg" for installing TQSL on a Mac. Having a signed >> installer increases the compatibility with current MacOS >> versions (Catalina and Big Sur). I'm very interested in >> feedback with these package files, as they're much easier >> to install. >> >> Download links below. >> Windows: >> https://www.rickmurphy.net/lotw/tqsl-2.5.6.msi >> <https://www.rickmurphy.net/lotw/tqsl-2.5.6.msi> >> >> Mac (64/32 bit, current systems) >> https://www.rickmurphy.net/lotw/tqsl-2.5.6.pkg >> <https://www.rickmurphy.net/lotw/tqsl-2.5.6.pkg> (Installer) >> https://www.rickmurphy.net/lotw/tqsl-2.5.6.dmg >> <https://www.rickmurphy.net/lotw/tqsl-2.5.6.dmg> (Disk image) >> >> Mac (Intel 386/Power PC legacy systems) >> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.pkg >> <https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.pkg> >> (Installer) >> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.dmg >> <https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.dmg> >> (Disk image) >> >> Linux/BSD: >> https://www.rickmurphy.net/lotw/tqsl-2.5.6.tar.gz >> <https://www.rickmurphy.net/lotw/tqsl-2.5.6.tar.gz> >> (source code only) >> 73, >> -Rick >> -- >> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >> >> >> _______________________________________________ >> Trustedqsl-testing mailing list >> Tru...@li... <mailto:Tru...@li...> >> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing <https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing> > _______________________________________________ > Trustedqsl-testing mailing list > Tru...@li... > <mailto:Tru...@li...> > https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing > <https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing> > > > > -- > Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA > > > > -- > Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA > > > > -- > Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA > > > _______________________________________________ > Trustedqsl-testing mailing list > Tru...@li... > https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing |
From: Rick M. <k1...@ar...> - 2020-11-01 18:08:08
|
This is an issue where TQSL is depending on an implicit conversion to wide characters that your system isn't allowing. Relying on implicit conversions can cause problems like this. I've checked in a correction to the repository. Patch to correct this is below. Thanks for reporting this. It wasn't at all what I thought. 73, -Rick diff --git a/apps/tqsl.cpp b/apps/tqsl.cpp index 1e9075c..f7a5d7d 100644 --- a/apps/tqsl.cpp +++ b/apps/tqsl.cpp @@ -745,7 +745,7 @@ class LogList : public wxLog { #if wxMAJOR_VERSION > 2 void LogList::DoLogText(const wxString& msg) { - const wxChar* szString(msg); + const wxChar* szString = msg.wc_str(); #else void LogList::DoLogString(const wxChar *szString, time_t) { static wxString msg(szString); @@ -789,7 +789,7 @@ class LogStderr : public wxLog { #if wxMAJOR_VERSION > 2 void LogStderr::DoLogText(const wxString& msg) { - const wxChar* szString(msg); + const wxChar* szString = msg.wc_str(); #else void LogStderr::DoLogString(const wxChar *szString, time_t) { static wxString msg(szString); @@ -5452,11 +5452,11 @@ QSLApp::OnInit() { wxString av = argv[0]; myArgv[0] = strdup(av.ToUTF8()); #else - myArgv[0] = strdup(argv[0]); + myArgv[0] = strdup(argv[0].ToUTF8()); #endif myArgc = 1; for (int i = 1; i < argc; i++) { - if ((const wxChar *)argv[i]) { + if ((const wxChar *)argv[i].mb_str().data()) { if ((i + 1) < argc) { wxString av1 = argv[i+1]; #if wxMAJOR_VERSION == 2 @@ -5471,9 +5471,9 @@ QSLApp::OnInit() { } origCommandLine += wxT(" "); #if wxMAJOR_VERSION == 2 - myArgv[myArgc] = strdup(wxString(argv[i]).ToUTF8());; + myArgv[myArgc] = strdup(wxString(argv[i]).ToUTF8()); #else - myArgv[myArgc] = strdup(argv[i]); + myArgv[myArgc] = strdup(argv[i].ToUTF8()); #endif #ifdef _WIN32 if (myArgv[myArgc][0] == '-' || myArgv[myArgc][0] == '/') On Sun, Nov 1, 2020 at 8:07 AM Rick Murphy <k1...@ar...> wrote: > I've reproduced this on an older version of openSUSE that I had a VM for > already. > Are you building against wxWidgets 2.x? Do you have 3.x libraries > available? 2.x is going to be end-of-life soon if not already - 2.8.12, > the latest 2.x release, came out in 2011. > 73, > -Rick > > On Sat, Oct 31, 2020 at 11:06 PM Rick Murphy <k1...@ar...> wrote: > >> What is your suggested fix? openSUSE has this problem for multiple >> wxWidgets consumers. For example, from 2016: >> https://forum.audacityteam.org/viewtopic.php?t=89971&start=10 >> >> I'll be happy to upstream a fix, but this seems to be a deliberate choice >> by openSuSE that leads to compatibility issues. >> 73, >> -Rick >> >> >> >> On Sat, Oct 31, 2020 at 10:47 PM Walter Fey <dl...@da...> wrote: >> >>> Compilation for openSUSE 15.2 and Tumbleweed fails. >>> The build logs with the error at the end are added to this mail. >>> >>> 73, >>> Walter DL8FCL >>> >>> >>> Am 31.10.20 um 19:06 schrieb Rick Murphy: >>> >>> I've published a release candidate for TQSL 2.5.6 - details below. >>> >>> Defects Corrected: >>> 1. In cases where applications pass empty passwords on the command line >>> (-p ""), TQSL could ignore that password and handle the command >>> incorrectly. This was not the behavior prior to TQSL 2.5.5. >>> 2. Ask the user to save a log being edited in the ADIF editor when they >>> close the editor window. Previously, TQSL would discard the file. >>> 3. TQSL more accurately prints the line number of an ADIF file with an >>> error message. In the past, TQSL always reported the line containing the >>> end-of-record tag. >>> >>> In addition, TQSL now uses the word "Passphrase" to distinguish between >>> the password used for the LoTW site and the passphrase used to secure a >>> Callsign Certificate. >>> >>> TQSL now also has a Swedish localization, thanks to SM0LTV. The other >>> localizations have also been updated. >>> >>> A big change in the packaging for TQSL 2.5.6 for MacOS is the use of a >>> signed and notarized (by Apple) package file ".pkg" for installing TQSL on >>> a Mac. Having a signed installer increases the compatibility with current >>> MacOS versions (Catalina and Big Sur). I'm very interested in feedback with >>> these package files, as they're much easier to install. >>> >>> Download links below. >>> Windows: >>> https://www.rickmurphy.net/lotw/tqsl-2.5.6.msi >>> >>> Mac (64/32 bit, current systems) >>> https://www.rickmurphy.net/lotw/tqsl-2.5.6.pkg (Installer) >>> https://www.rickmurphy.net/lotw/tqsl-2.5.6.dmg (Disk image) >>> >>> Mac (Intel 386/Power PC legacy systems) >>> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.pkg (Installer) >>> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.dmg (Disk image) >>> >>> Linux/BSD: >>> https://www.rickmurphy.net/lotw/tqsl-2.5.6.tar.gz (source code only) >>> 73, >>> -Rick >>> -- >>> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >>> >>> >>> _______________________________________________ >>> Trustedqsl-testing mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing >>> >>> _______________________________________________ >>> Trustedqsl-testing mailing list >>> Tru...@li... >>> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing >>> >> >> >> -- >> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >> > > > -- > Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA > -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1...@ar...> - 2020-11-01 13:08:21
|
I've reproduced this on an older version of openSUSE that I had a VM for already. Are you building against wxWidgets 2.x? Do you have 3.x libraries available? 2.x is going to be end-of-life soon if not already - 2.8.12, the latest 2.x release, came out in 2011. 73, -Rick On Sat, Oct 31, 2020 at 11:06 PM Rick Murphy <k1...@ar...> wrote: > What is your suggested fix? openSUSE has this problem for multiple > wxWidgets consumers. For example, from 2016: > https://forum.audacityteam.org/viewtopic.php?t=89971&start=10 > > I'll be happy to upstream a fix, but this seems to be a deliberate choice > by openSuSE that leads to compatibility issues. > 73, > -Rick > > > > On Sat, Oct 31, 2020 at 10:47 PM Walter Fey <dl...@da...> wrote: > >> Compilation for openSUSE 15.2 and Tumbleweed fails. >> The build logs with the error at the end are added to this mail. >> >> 73, >> Walter DL8FCL >> >> >> Am 31.10.20 um 19:06 schrieb Rick Murphy: >> >> I've published a release candidate for TQSL 2.5.6 - details below. >> >> Defects Corrected: >> 1. In cases where applications pass empty passwords on the command line >> (-p ""), TQSL could ignore that password and handle the command >> incorrectly. This was not the behavior prior to TQSL 2.5.5. >> 2. Ask the user to save a log being edited in the ADIF editor when they >> close the editor window. Previously, TQSL would discard the file. >> 3. TQSL more accurately prints the line number of an ADIF file with an >> error message. In the past, TQSL always reported the line containing the >> end-of-record tag. >> >> In addition, TQSL now uses the word "Passphrase" to distinguish between >> the password used for the LoTW site and the passphrase used to secure a >> Callsign Certificate. >> >> TQSL now also has a Swedish localization, thanks to SM0LTV. The other >> localizations have also been updated. >> >> A big change in the packaging for TQSL 2.5.6 for MacOS is the use of a >> signed and notarized (by Apple) package file ".pkg" for installing TQSL on >> a Mac. Having a signed installer increases the compatibility with current >> MacOS versions (Catalina and Big Sur). I'm very interested in feedback with >> these package files, as they're much easier to install. >> >> Download links below. >> Windows: >> https://www.rickmurphy.net/lotw/tqsl-2.5.6.msi >> >> Mac (64/32 bit, current systems) >> https://www.rickmurphy.net/lotw/tqsl-2.5.6.pkg (Installer) >> https://www.rickmurphy.net/lotw/tqsl-2.5.6.dmg (Disk image) >> >> Mac (Intel 386/Power PC legacy systems) >> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.pkg (Installer) >> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.dmg (Disk image) >> >> Linux/BSD: >> https://www.rickmurphy.net/lotw/tqsl-2.5.6.tar.gz (source code only) >> 73, >> -Rick >> -- >> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >> >> >> _______________________________________________ >> Trustedqsl-testing mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing >> >> _______________________________________________ >> Trustedqsl-testing mailing list >> Tru...@li... >> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing >> > > > -- > Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA > -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1...@ar...> - 2020-11-01 03:07:30
|
What is your suggested fix? openSUSE has this problem for multiple wxWidgets consumers. For example, from 2016: https://forum.audacityteam.org/viewtopic.php?t=89971&start=10 I'll be happy to upstream a fix, but this seems to be a deliberate choice by openSuSE that leads to compatibility issues. 73, -Rick On Sat, Oct 31, 2020 at 10:47 PM Walter Fey <dl...@da...> wrote: > Compilation for openSUSE 15.2 and Tumbleweed fails. > The build logs with the error at the end are added to this mail. > > 73, > Walter DL8FCL > > > Am 31.10.20 um 19:06 schrieb Rick Murphy: > > I've published a release candidate for TQSL 2.5.6 - details below. > > Defects Corrected: > 1. In cases where applications pass empty passwords on the command line > (-p ""), TQSL could ignore that password and handle the command > incorrectly. This was not the behavior prior to TQSL 2.5.5. > 2. Ask the user to save a log being edited in the ADIF editor when they > close the editor window. Previously, TQSL would discard the file. > 3. TQSL more accurately prints the line number of an ADIF file with an > error message. In the past, TQSL always reported the line containing the > end-of-record tag. > > In addition, TQSL now uses the word "Passphrase" to distinguish between > the password used for the LoTW site and the passphrase used to secure a > Callsign Certificate. > > TQSL now also has a Swedish localization, thanks to SM0LTV. The other > localizations have also been updated. > > A big change in the packaging for TQSL 2.5.6 for MacOS is the use of a > signed and notarized (by Apple) package file ".pkg" for installing TQSL on > a Mac. Having a signed installer increases the compatibility with current > MacOS versions (Catalina and Big Sur). I'm very interested in feedback with > these package files, as they're much easier to install. > > Download links below. > Windows: > https://www.rickmurphy.net/lotw/tqsl-2.5.6.msi > > Mac (64/32 bit, current systems) > https://www.rickmurphy.net/lotw/tqsl-2.5.6.pkg (Installer) > https://www.rickmurphy.net/lotw/tqsl-2.5.6.dmg (Disk image) > > Mac (Intel 386/Power PC legacy systems) > https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.pkg (Installer) > https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.dmg (Disk image) > > Linux/BSD: > https://www.rickmurphy.net/lotw/tqsl-2.5.6.tar.gz (source code only) > 73, > -Rick > -- > Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA > > > _______________________________________________ > Trustedqsl-testing mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing > > _______________________________________________ > Trustedqsl-testing mailing list > Tru...@li... > https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing > -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Walter F. <dl...@da...> - 2020-11-01 00:49:33
|
Compilation for openSUSE 15.2 and Tumbleweed fails. The build logs with the error at the end are added to this mail. 73, Walter DL8FCL Am 31.10.20 um 19:06 schrieb Rick Murphy: > I've published a release candidate for TQSL 2.5.6 - details below. > > Defects Corrected: > 1. In cases where applications pass empty passwords on the command > line (-p ""), TQSL could ignore that password and handle the command > incorrectly. This was not the behavior prior to TQSL 2.5.5. > 2. Ask the user to save a log being edited in the ADIF editor when > they close the editor window. Previously, TQSL would discard the file. > 3. TQSL more accurately prints the line number of an ADIF file with an > error message. In the past, TQSL always reported the line containing > the end-of-record tag. > > In addition, TQSL now uses the word "Passphrase" to distinguish > between the password used for the LoTW site and the passphrase used to > secure a Callsign Certificate. > > TQSL now also has a Swedish localization, thanks to SM0LTV. The other > localizations have also been updated. > > A big change in the packaging for TQSL 2.5.6 for MacOS is the use of a > signed and notarized (by Apple) package file ".pkg" for installing > TQSL on a Mac. Having a signed installer increases the compatibility > with current MacOS versions (Catalina and Big Sur). I'm very > interested in feedback with these package files, as they're much > easier to install. > > Download links below. > Windows: > https://www.rickmurphy.net/lotw/tqsl-2.5.6.msi > <https://www.rickmurphy.net/lotw/tqsl-2.5.6.msi> > > Mac (64/32 bit, current systems) > https://www.rickmurphy.net/lotw/tqsl-2.5.6.pkg > <https://www.rickmurphy.net/lotw/tqsl-2.5.6.pkg> (Installer) > https://www.rickmurphy.net/lotw/tqsl-2.5.6.dmg > <https://www.rickmurphy.net/lotw/tqsl-2.5.6.dmg> (Disk image) > > Mac (Intel 386/Power PC legacy systems) > https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.pkg > <https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.pkg> (Installer) > https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.dmg > <https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.dmg> (Disk image) > > Linux/BSD: > https://www.rickmurphy.net/lotw/tqsl-2.5.6.tar.gz > <https://www.rickmurphy.net/lotw/tqsl-2.5.6.tar.gz> (source code only) > 73, > -Rick > -- > Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA > > > _______________________________________________ > Trustedqsl-testing mailing list > Tru...@li... > https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing |
From: Rick M. <k1...@ar...> - 2020-10-31 19:06:41
|
I've published a release candidate for TQSL 2.5.6 - details below. Defects Corrected: 1. In cases where applications pass empty passwords on the command line (-p ""), TQSL could ignore that password and handle the command incorrectly. This was not the behavior prior to TQSL 2.5.5. 2. Ask the user to save a log being edited in the ADIF editor when they close the editor window. Previously, TQSL would discard the file. 3. TQSL more accurately prints the line number of an ADIF file with an error message. In the past, TQSL always reported the line containing the end-of-record tag. In addition, TQSL now uses the word "Passphrase" to distinguish between the password used for the LoTW site and the passphrase used to secure a Callsign Certificate. TQSL now also has a Swedish localization, thanks to SM0LTV. The other localizations have also been updated. A big change in the packaging for TQSL 2.5.6 for MacOS is the use of a signed and notarized (by Apple) package file ".pkg" for installing TQSL on a Mac. Having a signed installer increases the compatibility with current MacOS versions (Catalina and Big Sur). I'm very interested in feedback with these package files, as they're much easier to install. Download links below. Windows: https://www.rickmurphy.net/lotw/tqsl-2.5.6.msi Mac (64/32 bit, current systems) https://www.rickmurphy.net/lotw/tqsl-2.5.6.pkg (Installer) https://www.rickmurphy.net/lotw/tqsl-2.5.6.dmg (Disk image) Mac (Intel 386/Power PC legacy systems) https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.pkg (Installer) https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.6.dmg (Disk image) Linux/BSD: https://www.rickmurphy.net/lotw/tqsl-2.5.6.tar.gz (source code only) 73, -Rick -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1...@ar...> - 2020-08-05 02:14:54
|
I've released a TQSL 2.5.5 candidate. This update includes the following corrections: * When TQSL cannot find a matching Callsign Certificate for DXCC entity NONE when signing a log, add "None" to the resulting error message. Correct a defect where TQSL on Windows could hang if both a TQSL and a configuration file update appeared at the same time. Update the list of modes in the TQSL ADIF Editor to include all current modes. Allow the TQSL ADIF editor to retain all fields in an ADIF file, not just the ones Logbook stores. Correct handling of logs from Quebec, where Logbook uses the old "PQ" abbreviation versus the current "QC". Correct defects in TQSL when in "update" mode while signing a log to avoid crashes when a Callsign change caused zones, states, counties, etc. to become invalid. When processing a bad Cabrillo "QSO" record, if it cannot be parsed, discard it versus repeatedly displaying the same error and never completing. Accept full administrative subdivision names, so ADIF files with "New York" for MY_STATE versus the proper "NY" won't cause errors. When signing a log with multiple gridsquares and comparing to a station location, allow those gridsquares to be in arbitrary order. Most of these issues are relatively benign, but the issue with "QC" as a province is sufficiently impactful that I feel a new TQSL release is warranted. As always, any feedback on issues discovered while testing this release will help improve the quality of the final release. Comments both positive and negative very much appreciated. Links to kits: https://www.rickmurphy.net/lotw/tqsl-2.5.5.msi - Windows https://www.rickmurphy.net/lotw/tqsl-2.5.5.dmg - MacOS 64-bit https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.5.dmg - MacOS legacy 32-bit https://www.rickmurphy.net/lotw/tqsl-2.5.5.tar.gz - Linux/BSD 73, -Rick -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1m...@gm...> - 2020-05-10 13:54:15
|
This RC has a few fixes from 2.5.3: 1. Correct a defect that could cause some P12 files to fail to load. 2. Fix the matching for US Counties to be more accepting of variations of spelling, spaces, etc. 3. Fix the defect that causes random DXCC entity names to be displayed when a new TQSL config file is installed (until TQSL restarts) 4. Pass the DXCC entity to the address lookup server at ARRL for cases where a call is valid for multiple entities 5. Correct a defect where callsigns were treated as case-sensitive, meaning that <OPERATOR:4>k1mu would not match K1MU in the related callsign certificate. Available from the usual places: https://www.rickmurphy.net/lotw/tqsl-2.5.4.msi - Windows https://www.rickmurphy.net/lotw/tqsl-2.5.4. <https://www.rickmurphy.net/lotw/tqsl-2.5.4.msi>dmg - Mac (64-bit) https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.4.msi <https://www.rickmurphy.net/lotw/tqsl-2.5.4.msi> - Mac (32-bit) https://www.rickmurphy.net/lotw/tqsl-2.5.4. <https://www.rickmurphy.net/lotw/tqsl-2.5.4.msi>tar.gz - Linux/BSD 73, -Rick -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1...@ar...> - 2020-05-05 00:43:08
|
This RC has a few fixes from 2.5.3: 1. Correct a defect that could cause some P12 files to fail to load. 2. Fix the matching for US Counties to be more accepting of variations of spelling, spaces, etc. 3. Fix the defect that causes random DXCC entity names to be displayed when a new TQSL config file is installed (until TQSL restarts) Available from the usual places: https://www.rickmurphy.net/lotw/tqsl-2.5.4.msi - Windows https://www.rickmurphy.net/lotw/tqsl-2.5.4. <https://www.rickmurphy.net/lotw/tqsl-2.5.4.msi>dmg - Mac (64-bit) https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.4.msi <https://www.rickmurphy.net/lotw/tqsl-2.5.4.msi> - Mac (32-bit) https://www.rickmurphy.net/lotw/tqsl-2.5.4. <https://www.rickmurphy.net/lotw/tqsl-2.5.4.msi>tar.gz - Linux/BSD 73, -Rick -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1...@ar...> - 2020-04-11 22:13:54
|
I've published TQSL 2.5.3-rc1, which corrects several high-impact issues discovered this week in TQSL 2.5.2. The following corrections were made to correct these defects. 1. When a station has callsign certificates for multiple DXCC entities for the same callsign, TQSL could choose the wrong one. The correction ensures that the right DXCC entity is chosen. 2. When reading MY_CQZ and MY_ITUZ from a log (CQ and ITU Zones), leading zeroes would cause TQSL to think there was a mismatch. "05" is now treated the same as "5". 3. Loggers including extra characters in ADIF data could cause mismatches. TQSL now removes spaces from the beginning and end of data. 4. The OPERATOR tag in ADIF is frequently set as the name of the operator, not the callsign. TQSL now ignores anything that's not a plausible callsign. 5. TQSL and LoTW now allow 20 character callsigns, allowing the XX2020STAYHOME calls to now work. A defect when 14 character or longer callsigns are entered that would cause spurious data to appear in the callsign has been corrected. I intend to push the final TQSL 2.5.3 in the next several days. Please use the release candidate if any of the issues above are affecting you. Kits: https://www.rickmurphy.net/lotw/tqsl-2.5.3.msi - Windows https://www.rickmurphy.net/lotw/tqsl-2.5.3.dmg - MacOS 64-bit https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.3.dmg - MacOS 32-bit https://www.rickmurphy.net/lotw/tqsl-2.5.3.tar.gz - Linux/BSD 73, -Rick -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1...@ar...> - 2020-04-06 16:53:35
|
I've built the final TQSL 2.5.2 kits and published them. The primary new features of 2.5.2 relate to handling of QTH details, allowing TQSL to support roaming operations that weren't practical in the past, as well as being able to detect cases where stations sign logs using incorrect station locations. As usual, available from my webpage, or you can wait for the official signed kits from ARRL HQ. Release notes attached. https://www.rickmurphy.net/lotw/tqsl-2.5.2.msi - Windows https://www.rickmurphy.net/lotw/tqsl-2.5.2.dmg - Mac (64-bit) https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.2.msi - Mac (32-bit, PPC) https://www.rickmurphy.net/lotw/tqsl-2.5.2.tar.gz - Linux/BSD -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1...@ar...> - 2020-02-29 01:36:33
|
I've looked at Frank's log. The issue here is that this is a very large number of station locations, more than what LoTW is expecting. >From the 3285 QSOs there's 1230 different station locations (from 1117 different Gridsquares). LoTW allows up to 999 different station locations, and the one that hit the limit is the EA7ALL QSO. Once you hit 999, then the rest of the QSOs are using the same station location setup. I need to work with the HQ staff to get this limit increased. As far as the duplicate QSOs being discovered, they're interesting. For example, you have a QSO on 2018/02/27 at 1457 with a station from ML01ox then another QSO at the same time from ML02oa. Since the time is the same, TQSL considers this to be a dupe with an unexpected change of QTH. This is of course incorrect, as this QSO happened across adjacent grids. It would be better if the log emitted this as a single QSO with "MY_GRIDSQUARE" set to "ML01ox,ML02oa", but they're counted as "already uploaded" assuming they're the same QSO. This probably should be something that TQSL allows - another setting that indicates that the station roams across gridsquares and therefore grid changes are to be ignored. So this ran into a limit and I'll work to get that lifted. Cutting the log into two pieces will get past that limit. This has been really helpful in testing this new feature - it's going to make operations like yours so much easier to handle for LoTW uploads. 73, -Rick On Fri, Feb 28, 2020 at 3:22 PM Rick Murphy <k1...@ar...> wrote: > Frank, > The first thing you should look at is the log on the LoTW page that > describes what actions LoTW took when these logs were uploaded. > On the LoTW site, choose "Your Account", then "Your Activity". > Look at the "Result" link for one of your logs; you may see that LoTW was > rejecting some of these gridsquares. For example, LoTW has rules that > verify that grids are within the borders of various entities, and it may > have rejected some of your input. > 73, > -Rick > > On Fri, Feb 28, 2020 at 2:52 PM qsl F5MYK <qsl...@or...> wrote: > >> Hi Rick & All >> >> AA/ My mistake ! >> Thanks a lot for the message with the image.png. >> I am using a very old version of VQLog and the ADIF exporter writes >> own_gridsq instead of my_gridsquare. >> Much better now and very sorry for the inconvenience. >> >> May I suggest that if the user chooses "Override Station Location with >> QTH from the log", TQSL could ensure that the field MY_GRIDSQUARE is used >> at least for a few records ? >> >> >> BB/ New uploads : >> For years 2013 up to 2017, logs are less than 2000 QSO and it is OK. >> It seems that above 2500 lines (2018 & 2019) the upload is more difficult >> ? >> I searched in both logs without finding why my_gridsquare is not imported >> for all ADIF records. >> 2018 log: >> Line 1-5 are the ADIF header. >> Line 6 - 3290 are ADIF records. >> >> Line 2671 - EA7ALL - my locator is detailed NJ35BW >> Line 2672 - UA3QUP - my locator is missing NJ35CW ? >> I did not check for all QSO but the DB is populated with the next ~600 >> QSO except for my_gridsquare field ? >> >> I tried to find some difference between those lines but saw nothing >> special but the fact that the GL contains the string 'CW'? >> In case you need it, I will send this file to your private address. Hope >> it won't bother you... >> >> 2019 log: >> After a few tries I uploaded the first 5000 lines (only) and the same >> problem appears around line 2450. >> >> >> 73, Frank >> >> >> >> >> >> >> >> >> _______________________________________________ >> Trustedqsl-testing mailing list >> Tru...@li... >> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing >> > > > -- > Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA > -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1...@ar...> - 2020-02-28 20:22:43
|
Frank, The first thing you should look at is the log on the LoTW page that describes what actions LoTW took when these logs were uploaded. On the LoTW site, choose "Your Account", then "Your Activity". Look at the "Result" link for one of your logs; you may see that LoTW was rejecting some of these gridsquares. For example, LoTW has rules that verify that grids are within the borders of various entities, and it may have rejected some of your input. 73, -Rick On Fri, Feb 28, 2020 at 2:52 PM qsl F5MYK <qsl...@or...> wrote: > Hi Rick & All > > AA/ My mistake ! > Thanks a lot for the message with the image.png. > I am using a very old version of VQLog and the ADIF exporter writes > own_gridsq instead of my_gridsquare. > Much better now and very sorry for the inconvenience. > > May I suggest that if the user chooses "Override Station Location with QTH > from the log", TQSL could ensure that the field MY_GRIDSQUARE is used at > least for a few records ? > > > BB/ New uploads : > For years 2013 up to 2017, logs are less than 2000 QSO and it is OK. > It seems that above 2500 lines (2018 & 2019) the upload is more difficult ? > I searched in both logs without finding why my_gridsquare is not imported > for all ADIF records. > 2018 log: > Line 1-5 are the ADIF header. > Line 6 - 3290 are ADIF records. > > Line 2671 - EA7ALL - my locator is detailed NJ35BW > Line 2672 - UA3QUP - my locator is missing NJ35CW ? > I did not check for all QSO but the DB is populated with the next ~600 QSO > except for my_gridsquare field ? > > I tried to find some difference between those lines but saw nothing > special but the fact that the GL contains the string 'CW'? > In case you need it, I will send this file to your private address. Hope > it won't bother you... > > 2019 log: > After a few tries I uploaded the first 5000 lines (only) and the same > problem appears around line 2450. > > > 73, Frank > > > > > > > > > _______________________________________________ > Trustedqsl-testing mailing list > Tru...@li... > https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing > -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: qsl F. <qsl...@or...> - 2020-02-28 19:51:57
|
<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p><font size="+2">Hi Rick & All<br> <br> </font></p> <p><font size="+2">AA/ My mistake !<br> Thanks a lot for the message with the image.png.<br> I am using a very old version of VQLog and the ADIF exporter writes own_gridsq instead of my_gridsquare.<br> Much better now and very sorry for the inconvenience.<br> </font></p> <p><font size="+2">May I suggest that if the user chooses "Override Station Location with QTH from the log", TQSL could ensure that the field MY_GRIDSQUARE is used at least for a few records ?</font></p> <p><font size="+2"><br> BB/ New uploads :<br> For years 2013 up to 2017, logs are less than 2000 QSO and it is OK.<br> It seems that above 2500 lines (2018 & 2019) the upload is more difficult ?<br> I searched in both logs without finding why my_gridsquare is not imported for all ADIF records.</font></p> <font size="+2">2018 log:<br> Line 1-5 are the ADIF header.</font><br> <font size="+2">Line 6 - 3290 are ADIF records.<br> <br> Line 2671 - EA7ALL - my locator is detailed NJ35BW<br> Line 2672 - UA3QUP - my locator is missing NJ35CW ?<br> I did not check for all QSO but the DB is populated with the next ~600 QSO except for my_gridsquare field ?<br> </font> <p><font size="+2">I tried to find some difference between those lines but saw nothing special but the fact that the GL contains the string 'CW'?<br> In case you need it, I will send this file to your private address. Hope it won't bother you...<br> </font></p> <p><font size="+2">2019 log:<br> After a few tries I uploaded the first 5000 lines (only) and the same problem appears around line 2450.</font></p> <p><font size="+2"><br> </font></p> <p><font size="+2">73, Frank</font></p> <p><font size="+2"><br> </font></p> <p><font size="+2"><br> </font></p> <p><font size="+2"><br> </font></p> <p><font size="+2"> <br> </font></p> <p><font size="+2"><br> </font></p> <p><font size="+2"><br> </font></p> <p><font size="+2"></font><br> </p> </body> </html> |
From: Rick M. <k1...@ar...> - 2020-02-28 02:18:41
|
Frank, If your grid was uploaded, you would see that detail. For example, here's a QSO of mine (completely bogus, so I'm not giving anything away): [image: image.png] So, you should see the grid appearing in any QSOs you upload. 73, -Rick On Thu, Feb 27, 2020 at 9:02 PM qsl F5MYK <qsl...@or...> wrote: > Hi Rich and All, > > AA/ About the errors : > As I wrote my last message I tried to see the mistakes again without > success. > The first upload clearly stated the discrepancy between my Station > Location and the log. > For the second upload of the same log I am not sure I saw an explanation, > I only remember the error counter which was increasing quickly. > > BB/ I first tried to upload 21 QSO (year 2013) and then I upload the log > for the whole year 2013. > I had the message (quotation from memory) "21 QSO were already signed and > 300 are new". I chose the button "Upload the new QSO" and it was OK. > For the following years I only uploaded each file once. When I process the > logs I try to avoid logging the same station in the same minute when the > QSO took place on the 'locator edge' ... > > DD/ It is up to you but for moving stations this could be interesting to > show the locator registered with the QSO ? > Today I received 2 messages from Brazilian stations (extracts below), they > are not able to see my registered locators? > > QUOTE > > can you help me inform me your grid locators from this qsos? > 6m was a incredible qso because is blocked prop from here .. rare open > Details <https://lotw.arrl.org/lotwuser/qsodetail?qso=1100840367> PY7DJ > F5MYK/MM 2019-11-17 17:22:00 17M FT8 18.10050 -NONE- > <https://lotw.arrl.org/lotwuser/qsodetail?qso=1141279668> > Details <https://lotw.arrl.org/lotwuser/qsodetail?qso=1100125923> PY7DJ > F5MYK/MM 2019-11-15 17:38:00 15M FT8 21.07547 -NONE- > <https://lotw.arrl.org/lotwuser/qsodetail?qso=1141279342> > Details <https://lotw.arrl.org/lotwuser/qsodetail?qso=1100125920> PY7DJ > F5MYK/MM 2019-11-15 19:49:00 6M FT8 50.31475 -NONE- > <https://lotw.arrl.org/lotwuser/qsodetail?qso=1141279359> > Details <https://lotw.arrl.org/lotwuser/qsodetail?qso=802970480> PY7DJ > F5MYK/MM 2016-12-12 00:34:00 40M JT65 7.07600 -NONE- > <https://lotw.arrl.org/lotwuser/qsodetail?qso=1141259461> > > UNQUOTE > > QUOTE > > UNQUOTE > > I already explained that it is not a mistake as my DXCC was 'NONE', but it > seems that PY3TO does not know my locator. Idem for PY7DJ. > > > Using the QSO details I can see the locator of PY7DJ but I do not know if > he sees mine ? > > > Thanks again for all the work done, > > 73, Frank - f5myk > > > _______________________________________________ > Trustedqsl-testing mailing list > Tru...@li... > https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing > -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: qsl F. <qsl...@or...> - 2020-02-27 19:30:24
|
<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p>Hi Rich and All,</p> <p>AA/ About the errors :<br> As I wrote my last message I tried to see the mistakes again without success.<br> The first upload clearly stated the discrepancy between my Station Location and the log.<br> For the second upload of the same log I am not sure I saw an explanation, I only remember the error counter which was increasing quickly.</p> <p>BB/ I first tried to upload 21 QSO (year 2013) and then I upload the log for the whole year 2013.<br> I had the message (quotation from memory) "21 QSO were already signed and 300 are new". I chose the button "Upload the new QSO" and it was OK.<br> For the following years I only uploaded each file once. When I process the logs I try to avoid logging the same station in the same minute when the QSO took place on the 'locator edge' ... <br> </p> <p>DD/ It is up to you but for moving stations this could be interesting to show the locator registered with the QSO ?<br> Today I received 2 messages from Brazilian stations (extracts below), they are not able to see my registered locators?<br> </p> <p>QUOTE<br> </p> <p>can you help me inform me your grid locators from this qsos? <br> 6m was a incredible qso because is blocked prop from here .. rare open <br> </p> <table align="center"> <tbody> <tr> <td><a href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1100840367" target="_new">Details</a></td> <td>PY7DJ</td> <td>F5MYK/MM</td> <td style="text-align:center">2019-11-17 17:22:00</td> <td style="text-align:right">17M</td> <td style="text-align:center">FT8</td> <td style="text-align:right">18.10050</td> <td><a href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1141279668" target="_new">-NONE-</a></td> <td> </td> </tr> <tr> <td><a href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1100125923" target="_new">Details</a></td> <td>PY7DJ</td> <td>F5MYK/MM</td> <td style="text-align:center">2019-11-15 17:38:00</td> <td style="text-align:right">15M</td> <td style="text-align:center">FT8</td> <td style="text-align:right">21.07547</td> <td><a href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1141279342" target="_new">-NONE-</a></td> <td> </td> </tr> <tr> <td><a href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1100125920" target="_new">Details</a></td> <td>PY7DJ</td> <td>F5MYK/MM</td> <td style="text-align:center">2019-11-15 19:49:00</td> <td style="text-align:right">6M</td> <td style="text-align:center">FT8</td> <td style="text-align:right">50.31475</td> <td><a href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1141279359" target="_new">-NONE-</a></td> <td> </td> </tr> <tr> <td><a href="https://lotw.arrl.org/lotwuser/qsodetail?qso=802970480" target="_new">Details</a></td> <td>PY7DJ</td> <td>F5MYK/MM</td> <td style="text-align:center">2016-12-12 00:34:00</td> <td style="text-align:right">40M</td> <td style="text-align:center">JT65</td> <td style="text-align:right">7.07600</td> <td><a href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1141259461" target="_new">-NONE-</a></td> <td> </td> </tr> </tbody> </table> <p>UNQUOTE</p> <p>QUOTE</p> <p><img src="cid:par...@or..." alt=""></p> UNQUOTE<br> <p>I already explained that it is not a mistake as my DXCC was 'NONE', but it seems that PY3TO does not know my locator. Idem for PY7DJ.<br> </p> <p><br> </p> <p>Using the QSO details I can see the locator of PY7DJ but I do not know if he sees mine ?</p> <p><img src="cid:par...@or..." alt=""></p> <p><br> </p> <p>Thanks again for all the work done,</p> <p>73, Frank - f5myk<br> </p> <p><br> </p> </body> </html> |
From: Rick M. <k1...@ar...> - 2020-02-27 13:33:47
|
On Thu, Feb 27, 2020 at 6:26 AM qsl F5MYK <qsl...@or...> wrote: > Dear All, > > Back in Nantes, I uploaded my /MM log yesterday evening using TQSL 2.5.2. > AA/ First test with 21 QSO, 7 locators (4 characters) and “Report on QTH > difference” radio-button checked: > After a first scan of the log I had 21 mismatches reported which is > normal as my Station Location is F5MYK/MM and locator is null. Trying to > upload the same file again I entered an endless loop and canceled the > operation after more than 10000+ errors. Solved after a stop/start of the > software. > Do you recall what those errors were? I'd like to understand what caused this error. The problem reported by Walter earlier this week would cause an error message loop ("Unable to open ca-bundle.crt. Your TQSL installation is incomplete"), which I've now fixed. So, if it's that, then the cause is known. > BB/ With option “Override station location with QTH details from the log” > checked: > I sliced my log into 5 files (from 250 QSO up to 20000) and uploaded with > TQSL. In some cases TQSL reported that “n QSO were already signed...” but I > never uploaded those files before? > The "Already Uploaded" can be reported for duplicated QSOs. For example, if you sign a QSO with a given station and a bit later try to sign that same QSO, it'll be reported as "previously uploaded" even if that actually never made it to Logbook. CC/ The stats: > from my VQLOG 26586 QSO including 375 SWL reports (beacons, heard but no > QSO etc…). > LoTW log is now 26483 and the delta with VQLog is 103. > I doubt I have more than 100 QSO showing same > Date/Time/Band/Mode/Gridsquare/MyGridsquare but who knows? Anyway it is > less than 0.5%. > Not bad. > DD/ Suggested upgrades? > - For the present I am not sure I can check that the stations in my log > are credited of my varying locators ? > By this, I assume you mean that your QSOs were uploaded with the proper locators. You can query a QSO on the Logbook page and see the details there, or you can download your log from LoTW and check the QSO details in that download. It appears that you've verified this using VQLOG, though. > > To show both locators in the QSO details cards and records per > call queries… > Here, I think you mean with QSLs - showing full details of both your QTH and that of whom you've worked. But I'm not sure what you're asking for. Can you elaborate? > With the reserves in my /DD, my conclusion as a /MM user is that the > version 2.5.2 could be a giant step forward! > Thanks, 73 -Rick > > Thanks a lot, > 73, Frank - f5myk > > > > _______________________________________________ > Trustedqsl-testing mailing list > Tru...@li... > https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing > -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: qsl F. <qsl...@or...> - 2020-02-27 10:42:54
|
<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p><font size="+1"> Dear All,</font></p> <p><font size="+1">Back in Nantes, I uploaded my /MM log yesterday evening using TQSL 2.5.2. </font></p> <font size="+1"> </font><font size="+1"><span lang="en-US">AA/ First test with 21 QSO, 7 locators (4 characters) </span><span lang="en-US">and “</span><span lang="en-US">Report on QTH difference” radio-button checked</span><span lang="en-US">:</span><span lang="en-US"><br> After a first </span><span lang="en-US">scan</span><span lang="en-US"> of the log I had 21 mismatches reported </span><span lang="en-US">which</span><span lang="en-US"> is normal as my Station Location is F5MYK/MM and locator is null. Trying to upload the same file again I entered an endless loop </span><span lang="en-US">and </span><span lang="en-US">canceled the operation </span><span lang="en-US">after more than 10000+ errors. </span><span lang="en-US">Solved after a stop/start of the software.</span></font><br> <font size="+1"> </font><br> <font size="+1"><span lang="en-US">BB/ With option “Override station location with QTH details from the log” checked:<br> </span></font><font size="+1"><span lang="en-US">I </span><span lang="en-US">sliced my log into 5 files (from 250 QSO up to 20000) and uploaded with TQSL. In some cases TQSL reported that “n QSO were already signed...” but I never uploaded those files before?<br> <br> CC/ The stats:<br> </span></font><font size="+1"><span lang="en-US">from my VQLOG 26586 QSO including 375 SWL reports (beacons, heard but no QSO etc…).</span></font><br> <font size="+1"> </font><font size="+1"><span lang="en-US">LoTW log is now 26483 and the delta with VQLog is 103. </span></font> <br> <font size="+1"> </font><font size="+1"><span lang="en-US">I doubt I have more than 100 QSO showing same Date/Time/Band/Mode/Gridsquare/MyGridsquare </span><span lang="en-US">but who knows</span><span lang="en-US">? </span><span lang="en-US">Anyway it is less than 0.5%.</span></font><br> <font size="+1"> </font><font size="+1"><span lang="en-US"><br> DD/ </span><span lang="en-US">Suggested upgrades?</span></font><br> <font size="+1"> </font><font size="+1"><span lang="en-US">- For the present I am not sure I can check that the stations in my log are credited of my varying locators ?</span></font><br> <font size="+1"> </font><font size="+1"><span lang="en-US">> To show both locators in the QSO details cards and records per call queries…<br> </span></font><br> <font size="+1"><span lang="en-US">With the reserves in my /DD, my conclusion as a /MM user is that the version 2.5.2 could be a giant step forward!<br> </span><br> </font> <font size="+1"><span lang="en-US">Thanks a lot,</span></font><br> <font size="+1"> </font><font size="+1"><span lang="en-US">73, Frank - f5myk<br> </span><br> </font> <br> <font size="+1"> </font> <p style="margin-bottom: 0cm; line-height: 100%"><font size="+1"><br> </font> </p> <font size="+1"> </font> </body> </html> |
From: Rick M. <k1...@ar...> - 2020-02-25 01:16:58
|
For the record - Walter provided a log, proving that this is indeed a TQSL defect. If TQSL isn't able to open the file "ca-bundle.crt", which is typically bundled with the tqsl program, it gets stuck in a loop. That file is not commonly installed on Linux systems as the system bundle is used. I have a patch, or you can install ca-bundle.crt into your TQSL working directory. 73, -Rick On Mon, Feb 24, 2020 at 11:26 AM Rick Murphy <k1...@ar...> wrote: > I've just verified on Fedora; command line signing and uploading a log > worked fine. > I suspect you've got a tqsl dialog box appearing that's blocking the > signing operation - the diagnostic trace would indicate where. > 73, > -Rick > > On Mon, Feb 24, 2020 at 11:11 AM Rick Murphy <k1...@ar...> wrote: > >> On Mon, Feb 24, 2020 at 10:51 AM Walter Fey <dl...@da...> wrote: >> >>> The upload of does not work on openSUSE Leap 15.1. >>> >>> I tried a simple adi file, exported from XLOG without a "MY_" field, and >>> a wsjtx_log.adi written with WSJTX and JTDX with the "my_gridsquare" >>> information. I can start the program, do all inputs necessary, press the >>> button that only new QSOs shall be uploaded and than nothing is happening >>> anymore until I kill the process. >>> >> Walter, >> Is this a case where you're trying to sign and upload a file exported >> from XLOG using tqsl directly, or is this a case where xlog is driving a >> tqsl command line to do the upload? >> >> If you're doing this directly using tqsl, a diagnostic log would be >> helpful. >> If you're driving tqsl from XLOG, having the command line details would >> also be helpful; ideally add "-t tqsldiag.log" to get a diag log here as >> well. >> 73, >> -Rick >> >>> 73, Walter DL8FCL >>> >>> >>> Am 24.02.20 um 10:23 schrieb Rick Murphy: >>> >>> Correction - it's 2.5.2, not 2.5.3, so files are here: >>> https://www.rickmurphy.net/lotw/tqsl-2.5.2.msi - Windows >>> https://www.rickmurphy.net/lotw/tqsl-2.5.2.dmg - OSX 64-bit >>> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.2.dmg - OSX 32-bit >>> legacy >>> https://www.rickmurphy.net/lotw/tqsl-2.5.2.tar.gz - Linux/BSD/etc. >>> >>> 73, >>> -Rick >>> >>> >>> On Sun, Feb 23, 2020 at 9:36 PM Rick Murphy <k1...@ar...> wrote: >>> >>>> A new version of TQSL is available for testing. >>>> I would very much like logger developers to test this release, along >>>> with the new features for handling QTH updates from ADIF logs. >>>> >>>> The primary drive for this release is to allow a log being signed by >>>> TQSL to take notice of the "MY_" fields in an ADIF file, using that data to >>>> verify or update the Station Location used when signing a log. This will >>>> allow operations such as VHF roaming to export things like gridsquares on a >>>> per-QSO basis. It will also allow a logger to emit information that can be >>>> used to help prevent users from uploading "Zombie" QSOs into Logbook. >>>> >>>> Fields from ADIF used to validate station location information include >>>> >>>> MY_CNTY - County (Secondary Administrative Subdivision) >>>> MY_COUNTRY - DXCC Entity (May be overridden by MY_DXCC) >>>> MY_CQ_ZONE - CQ Zone >>>> MY_DXCC - DXCC Entity >>>> MY_GRIDSQUARE - Station Grid Square (may be overridden by >>>> MY_VUCC_GRIDS) >>>> MY_IOTA - IOTA Identifier >>>> MY_ITU_ZONE - ITU Zone >>>> MY_STATE - State (Primary Adminstrative Subdivision) >>>> MY_VUCC_GRIDS - Grid set >>>> OPERATOR - Station Callsign >>>> STATION_CALLSIGN- Station Callsign >>>> OWNER_CALLSIGN - Station Callsign >>>> >>>> The "Station Callsign" is chosen from STATION_CALLSIGN (if set), >>>> OWNER_CALLSIGN, then OPERATOR. (i.e.OPERATOR has precedence, then OWNER, >>>> then STATION). >>>> >>>> Control of how the QTH data from the ADIF log is handled is either >>>> specified by a command line argument or by a TQSL preference. The "-f" (or >>>> --verify) argument can be set to "-f ignore" (ignore ADIF QTH fields), "-f >>>> report" (Report on any discrepancies between the ADIF QTH data and the >>>> chosen Station Location) or "-f update", which updates the Station Location >>>> temporarily. >>>> >>>> There's a preference setting for log handling, part of a new "Log >>>> Handling" preference tab. This preference setting is not used for command >>>> line operations. The default in both cases is to report on QTH differences. >>>> >>>> I expect this capability to be very useful for roaming stations, as >>>> well as being of interest to stations using loggers that record >>>> Gridsquares, such as WSJT-X. >>>> >>>> That being said, none of this will have any impact unless logging >>>> programs export the QTH info in the ADIF fields above. Please give this a >>>> try, as it allows a logger to take better control of what gets uploaded to >>>> Logbook. If it works, or doesn't, please send me feedback. >>>> Thanks! >>>> >>>> Files in the usual locations: >>>> >>>> https://www.rickmurphy.net/lotw/tqsl-2.5.3.msi - Windows >>>> https://www.rickmurphy.net/lotw/tqsl-2.5.3.dmg - OSX 64-bit >>>> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.3.msi - OSX 32-bit >>>> legacy >>>> https://www.rickmurphy.net/lotw/tqsl-2.5.3.tar.gz - Linux/BSD/etc. >>>> >>>> 73, >>>> -Rick >>>> -- >>>> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >>>> >>> >>> >>> -- >>> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >>> >>> >>> _______________________________________________ >>> Trustedqsl-testing mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing >>> >>> _______________________________________________ >>> Trustedqsl-testing mailing list >>> Tru...@li... >>> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing >>> >> >> >> -- >> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >> > > > -- > Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA > -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1...@ar...> - 2020-02-24 16:27:31
|
I've just verified on Fedora; command line signing and uploading a log worked fine. I suspect you've got a tqsl dialog box appearing that's blocking the signing operation - the diagnostic trace would indicate where. 73, -Rick On Mon, Feb 24, 2020 at 11:11 AM Rick Murphy <k1...@ar...> wrote: > On Mon, Feb 24, 2020 at 10:51 AM Walter Fey <dl...@da...> wrote: > >> The upload of does not work on openSUSE Leap 15.1. >> >> I tried a simple adi file, exported from XLOG without a "MY_" field, and >> a wsjtx_log.adi written with WSJTX and JTDX with the "my_gridsquare" >> information. I can start the program, do all inputs necessary, press the >> button that only new QSOs shall be uploaded and than nothing is happening >> anymore until I kill the process. >> > Walter, > Is this a case where you're trying to sign and upload a file exported > from XLOG using tqsl directly, or is this a case where xlog is driving a > tqsl command line to do the upload? > > If you're doing this directly using tqsl, a diagnostic log would be > helpful. > If you're driving tqsl from XLOG, having the command line details would > also be helpful; ideally add "-t tqsldiag.log" to get a diag log here as > well. > 73, > -Rick > >> 73, Walter DL8FCL >> >> >> Am 24.02.20 um 10:23 schrieb Rick Murphy: >> >> Correction - it's 2.5.2, not 2.5.3, so files are here: >> https://www.rickmurphy.net/lotw/tqsl-2.5.2.msi - Windows >> https://www.rickmurphy.net/lotw/tqsl-2.5.2.dmg - OSX 64-bit >> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.2.dmg - OSX 32-bit legacy >> https://www.rickmurphy.net/lotw/tqsl-2.5.2.tar.gz - Linux/BSD/etc. >> >> 73, >> -Rick >> >> >> On Sun, Feb 23, 2020 at 9:36 PM Rick Murphy <k1...@ar...> wrote: >> >>> A new version of TQSL is available for testing. >>> I would very much like logger developers to test this release, along >>> with the new features for handling QTH updates from ADIF logs. >>> >>> The primary drive for this release is to allow a log being signed by >>> TQSL to take notice of the "MY_" fields in an ADIF file, using that data to >>> verify or update the Station Location used when signing a log. This will >>> allow operations such as VHF roaming to export things like gridsquares on a >>> per-QSO basis. It will also allow a logger to emit information that can be >>> used to help prevent users from uploading "Zombie" QSOs into Logbook. >>> >>> Fields from ADIF used to validate station location information include >>> >>> MY_CNTY - County (Secondary Administrative Subdivision) >>> MY_COUNTRY - DXCC Entity (May be overridden by MY_DXCC) >>> MY_CQ_ZONE - CQ Zone >>> MY_DXCC - DXCC Entity >>> MY_GRIDSQUARE - Station Grid Square (may be overridden by MY_VUCC_GRIDS) >>> MY_IOTA - IOTA Identifier >>> MY_ITU_ZONE - ITU Zone >>> MY_STATE - State (Primary Adminstrative Subdivision) >>> MY_VUCC_GRIDS - Grid set >>> OPERATOR - Station Callsign >>> STATION_CALLSIGN- Station Callsign >>> OWNER_CALLSIGN - Station Callsign >>> >>> The "Station Callsign" is chosen from STATION_CALLSIGN (if set), >>> OWNER_CALLSIGN, then OPERATOR. (i.e.OPERATOR has precedence, then OWNER, >>> then STATION). >>> >>> Control of how the QTH data from the ADIF log is handled is either >>> specified by a command line argument or by a TQSL preference. The "-f" (or >>> --verify) argument can be set to "-f ignore" (ignore ADIF QTH fields), "-f >>> report" (Report on any discrepancies between the ADIF QTH data and the >>> chosen Station Location) or "-f update", which updates the Station Location >>> temporarily. >>> >>> There's a preference setting for log handling, part of a new "Log >>> Handling" preference tab. This preference setting is not used for command >>> line operations. The default in both cases is to report on QTH differences. >>> >>> I expect this capability to be very useful for roaming stations, as well >>> as being of interest to stations using loggers that record Gridsquares, >>> such as WSJT-X. >>> >>> That being said, none of this will have any impact unless logging >>> programs export the QTH info in the ADIF fields above. Please give this a >>> try, as it allows a logger to take better control of what gets uploaded to >>> Logbook. If it works, or doesn't, please send me feedback. >>> Thanks! >>> >>> Files in the usual locations: >>> >>> https://www.rickmurphy.net/lotw/tqsl-2.5.3.msi - Windows >>> https://www.rickmurphy.net/lotw/tqsl-2.5.3.dmg - OSX 64-bit >>> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.3.msi - OSX 32-bit >>> legacy >>> https://www.rickmurphy.net/lotw/tqsl-2.5.3.tar.gz - Linux/BSD/etc. >>> >>> 73, >>> -Rick >>> -- >>> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >>> >> >> >> -- >> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >> >> >> _______________________________________________ >> Trustedqsl-testing mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing >> >> _______________________________________________ >> Trustedqsl-testing mailing list >> Tru...@li... >> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing >> > > > -- > Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA > -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |
From: Rick M. <k1...@ar...> - 2020-02-24 16:11:50
|
On Mon, Feb 24, 2020 at 10:51 AM Walter Fey <dl...@da...> wrote: > The upload of does not work on openSUSE Leap 15.1. > > I tried a simple adi file, exported from XLOG without a "MY_" field, and a > wsjtx_log.adi written with WSJTX and JTDX with the "my_gridsquare" > information. I can start the program, do all inputs necessary, press the > button that only new QSOs shall be uploaded and than nothing is happening > anymore until I kill the process. > Walter, Is this a case where you're trying to sign and upload a file exported from XLOG using tqsl directly, or is this a case where xlog is driving a tqsl command line to do the upload? If you're doing this directly using tqsl, a diagnostic log would be helpful. If you're driving tqsl from XLOG, having the command line details would also be helpful; ideally add "-t tqsldiag.log" to get a diag log here as well. 73, -Rick > 73, Walter DL8FCL > > > Am 24.02.20 um 10:23 schrieb Rick Murphy: > > Correction - it's 2.5.2, not 2.5.3, so files are here: > https://www.rickmurphy.net/lotw/tqsl-2.5.2.msi - Windows > https://www.rickmurphy.net/lotw/tqsl-2.5.2.dmg - OSX 64-bit > https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.2.dmg - OSX 32-bit legacy > https://www.rickmurphy.net/lotw/tqsl-2.5.2.tar.gz - Linux/BSD/etc. > > 73, > -Rick > > > On Sun, Feb 23, 2020 at 9:36 PM Rick Murphy <k1...@ar...> wrote: > >> A new version of TQSL is available for testing. >> I would very much like logger developers to test this release, along with >> the new features for handling QTH updates from ADIF logs. >> >> The primary drive for this release is to allow a log being signed by TQSL >> to take notice of the "MY_" fields in an ADIF file, using that data to >> verify or update the Station Location used when signing a log. This will >> allow operations such as VHF roaming to export things like gridsquares on a >> per-QSO basis. It will also allow a logger to emit information that can be >> used to help prevent users from uploading "Zombie" QSOs into Logbook. >> >> Fields from ADIF used to validate station location information include >> >> MY_CNTY - County (Secondary Administrative Subdivision) >> MY_COUNTRY - DXCC Entity (May be overridden by MY_DXCC) >> MY_CQ_ZONE - CQ Zone >> MY_DXCC - DXCC Entity >> MY_GRIDSQUARE - Station Grid Square (may be overridden by MY_VUCC_GRIDS) >> MY_IOTA - IOTA Identifier >> MY_ITU_ZONE - ITU Zone >> MY_STATE - State (Primary Adminstrative Subdivision) >> MY_VUCC_GRIDS - Grid set >> OPERATOR - Station Callsign >> STATION_CALLSIGN- Station Callsign >> OWNER_CALLSIGN - Station Callsign >> >> The "Station Callsign" is chosen from STATION_CALLSIGN (if set), >> OWNER_CALLSIGN, then OPERATOR. (i.e.OPERATOR has precedence, then OWNER, >> then STATION). >> >> Control of how the QTH data from the ADIF log is handled is either >> specified by a command line argument or by a TQSL preference. The "-f" (or >> --verify) argument can be set to "-f ignore" (ignore ADIF QTH fields), "-f >> report" (Report on any discrepancies between the ADIF QTH data and the >> chosen Station Location) or "-f update", which updates the Station Location >> temporarily. >> >> There's a preference setting for log handling, part of a new "Log >> Handling" preference tab. This preference setting is not used for command >> line operations. The default in both cases is to report on QTH differences. >> >> I expect this capability to be very useful for roaming stations, as well >> as being of interest to stations using loggers that record Gridsquares, >> such as WSJT-X. >> >> That being said, none of this will have any impact unless logging >> programs export the QTH info in the ADIF fields above. Please give this a >> try, as it allows a logger to take better control of what gets uploaded to >> Logbook. If it works, or doesn't, please send me feedback. >> Thanks! >> >> Files in the usual locations: >> >> https://www.rickmurphy.net/lotw/tqsl-2.5.3.msi - Windows >> https://www.rickmurphy.net/lotw/tqsl-2.5.3.dmg - OSX 64-bit >> https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.3.msi - OSX 32-bit legacy >> https://www.rickmurphy.net/lotw/tqsl-2.5.3.tar.gz - Linux/BSD/etc. >> >> 73, >> -Rick >> -- >> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA >> > > > -- > Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA > > > _______________________________________________ > Trustedqsl-testing mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing > > _______________________________________________ > Trustedqsl-testing mailing list > Tru...@li... > https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing > -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA |