trustedqsl-testing — for use in reporting defects in the TQSL and TQSLCert applications, and in the TrustedQSL library

[Trustedqsl-testing] Final TQSL 2.8.2 release candidate

[Rick M. <k1...@ar...>]

I've made a minor update to TQSL and I've built a new release candidate for
testing prior to the final release.  TQSL 2.8.2-rc4 has a change where the
error message for "The selected station location could not be found" now
has the name of the station location included.

While this is a small change, I've learned from painful experience that
small changes aren't always as simple as they appear, so there's a new RC
to allow checking that I haven't missed anything.

Kits available from the usual places:

https://www.rickmurphy.net/lotw/tqsl-2.8.2.msi - Windows
https://www.rickmurphy.net/lotw/tqsl-2.8.2.pkg - Mac
https://www.rickmurphy.net/lotw/tqsl--legacy-2.8.2.pkg - Intel/PowerPC
32-bit Mac
https://www.rickmurphy.net/lotw/tqsl-2.8.2.tar.gz - BSD/Linux
73,
    -Rick
-- 
Rick Murphy, D.Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

[Trustedqsl-testing] TQSL 2.8.2 release candidate avaialblle for testing

[Rick M. <k1...@ar...>]

I'm issuing a release candidate for TQSL 2.8.2
There's been a lot of focus in this release on removing the bloat that TQSL
has gained over the years as the RAM it consumes is starting to impact
users with random crashes and other instability. I want to thank M0OXO for
his help with validating these fixes as well as motivating the work to
clean this up.

Primary changes:
- After instrumentation of TQSL searching for memory "leaks", made several
changes to decrease memory usage.

- When signing a log, store the signed output to disk rather than in
memory as large logs could consume excessive RAM.

- Decrease the possibility of out-of-memory errors for QSL managers with
many active callsign certificates when requesting a new callsign
certificate by adding a default preference setting.

- Add ability for a local prefix database to override the one installed
with TQSL.

- Detect missing vuccgrids.dat file and report. Disable grid square
validation for this case.

- Add missing export definitions for 32-bit tqsslib DLL on Windows. (Thanks
to Jordi, EA3GCV for reporting this).

- Ignore VUCC grid checks for DXCC entity "None".

- Correct handling of grids found to be inconsistent to allow a second
click to properly save that entry.

Callsign prefix fixes:
- Add VK2 as a valid prefix for Lord Howe Island portable operations.
- Add callsign prefix mapping for VO for Canada, not just "Newfoundland
Labrador (Deleted)".
- Fix GB prefix to map it to any UK entity.

Kits in the usual place
https://www.rickmurphy.net/lotw/tqsl-2.8.2.msi  - Windows
https://www.rickmurphy.net/lotw/tqsl-2.8.2.pkg  - Mac 64-bit (Intel/Apple
Silicon)
https://www.rickmurphy.net/lotw/tqsl-legacy-2.8.2.pkg  - Mac 32-bit (Intel,
PowerPC)
https://www.rickmurphy.net/lotw/tqsl-2.8.2.tar.gz - Linux/BSD
73,
    -Rick


-- 
Rick Murphy, D.Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: [Trustedqsl-testing] zh_CN Translation error "Restore Deleted Callsign Certificate"

[Rick M. <k1...@ar...>]

Thanks.
Fix pushed to the repository. This fix will be included in the next TQSL
release (2.8.2).
73,
    -Rick

On Tue, Jul 15, 2025 at 5:31 AM Haowu Ge via Trustedqsl-testing <
tru...@li...> wrote:

> Hello developers,
> I found a translation error.
> The original translation was "回复删除的呼号证书", but the correct translation
> should be "恢复删除的呼号证书".
> Thank you.
>
>
> https://sourceforge.net/p/trustedqsl/tqsl/ci/master/tree/apps/lang/zh_CN/tqslapp.po#l2314
> #: tqsl.cpp:6498
> msgid "Restore Deleted Callsign Certificate"
> msgstr "回复删除的呼号证书"
>
>
> Thanks & Best Regards
> _________________________________________________________________________________
>
> Haowu Ge | Homepage: https://www.gehaowu.com | PGP:7A06 1F6E DF09 D8A8
> _______________________________________________
> Trustedqsl-testing mailing list
> Tru...@li...
> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>


-- 
Rick Murphy, D.Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

[Trustedqsl-testing] zh_CN Translation error "Restore Deleted Callsign Certificate"

[Haowu G. <ge...@bi...>]

Hello developers, 
I found a translation error. 
The original translation was "回复删除的呼号证书", but the correct translation should be "恢复删除的呼号证书".
Thank you.

https://sourceforge.net/p/trustedqsl/tqsl/ci/master/tree/apps/lang/zh_CN/tqslapp.po#l2314
#: tqsl.cpp:6498
msgid "Restore Deleted Callsign Certificate"
msgstr "回复删除的呼号证书"


Thanks & Best Regards
_________________________________________________________________________________ 
Haowu Ge | Homepage: https://www.gehaowu.com | PGP:7A06 1F6E DF09 D8A8

Re: [Trustedqsl-testing] TQSL 2.8 Beta available for testing

[<da...@do...>]

> On Apr 24, 2025, at 12:56 PM, Rick Murphy <k1...@ar...> wrote:
> 
> Is this consistently happening?  Or is upload working properly some of the time and not others?

So far it’s only 2 of our users with lot’s of others reporting no problems.

73 de VE3VRW Don Agro

Re: [Trustedqsl-testing] TQSL 2.8 Beta available for testing

[Rick M. <k1...@ar...>]

On Thu, Apr 24, 2025 at 10:38 AM da...@do... <
da...@do...> wrote:

>
> There is no error listed between “*Signing using Callsign...*” and “*No
> QSOs to upload"*
>

That's been reported on ARRL-LOTW - perhaps another MacLoggerDX user but
that's not important.
I'm looking into this, specifically trying to figure out where this can end
up silently saying "No QSOs to upload".
Clearly something sneaked in here during 2.8 development - the "Test
Signing a log" changes are suspect.

Is this consistently happening?  Or is upload working properly some of the
time and not others?
73,
    -Rick
-- 
Rick Murphy, D.Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: [Trustedqsl-testing] TQSL 2.8 Beta available for testing

[<da...@do...>]

Hi Rick,

I’m the developer of MacLoggerDX and have been using tqsl in command line mode since 2017. Works great!

Today I heard from 2 customers who upgraded to tqsl v2.8 and MacLoggerDX uploads stopped working.

I should note that the beta and 2.8 release work fine for me here but that these customers are getting very short (4 line) error messages back from tqsl.

They are able to export the ADIF from MacLoggerDX, sign and upload them directly with tqsl with no problem.

There is no error listed between “Signing using Callsign...” and “No QSOs to upload"

This is what they are getting …

2025-04-23 19:39:30.197 MacLoggerDX[8687:373996] postNewQSOToLoTWRealTime:response:numlines:[4] lines:[(
    "TQSL Version 2.8 [v2.8]",
    "Signing using Callsign W7SAG, DXCC Entity UNITED STATES OF AMERICA",
    "No QSOs to upload",
    "Final Status: No QSOs to upload(8)"
)]

2025-04-24 07:35:10.210 MacLoggerDX[61138:5364493] postNewQSOToLoTWRealTime:response:numlines:[4] lines:[(
    "TQSL Version 2.8 [v2.8]",
    "Signing using Callsign KK7A, DXCC Entity UNITED STATES OF AMERICA",
    "No QSOs to upload",
    "Final Status: No QSOs to upload(8)"
)]


This is what they should see…

2025-04-24 09:47:57.869 MacLoggerDX[29032:10610082] postNewQSOToLoTWRealTime:response:numlines:[7] lines:[(
    "TQSL Version 2.8 [v2.8]",
    "Signing using Callsign VE3VRW, DXCC Entity CANADA",
    "Attempting to upload one QSO",
    "/var/folders/wq/vwmp53251zldmtxdr9nm1h800000gn/T/KD2X_D8E20FED-EF51-458C-AE9C-97F01393DE4F_mldx_lotw.adi: Log uploaded successfully with result:",
    "File queued for processing",
    "After reading this message, you may close this program.",
    "Final Status: Success(0)"
)]


Here is a sample of the command line used …

commandLine:["/Applications/TrustedQSL/tqsl v2.8.app/Contents/MacOS/tqsl" -d -u -a all -x -c "VE3VRW" -l "8 Cliffcrest" "/var/folders/wq/vwmp53251zldmtxdr9nm1h800000gn/T/VK3ARR_CF950D23-78BE-4427-B6B2-ED415BFA6963_mldx_lotw.adi"]



73 de VE3VRW Don Agro

[Trustedqsl-testing] TQSL 2.8 Beta available for testing

[Rick M. <k1...@ar...>]

I've published a test version of the next version of TQSL for testing with
your applications.

Changes:
o TQSL 2.8 has a major improvement in Callsign Certificate request handling
- it now has a database of callsign prefixes and limits the list of
Entities shown when requesting a callsign certificate to only the relevant
entries, usually avoiding long scrolling to get to entities (for example,
USA, which was way down the list.)

o The flow for callsign certificate request handling now asks what the
certificate is for (former callsign, club, etc.) and provides additional
guidance on when to "sign" a request.

o When starting TQSL from a clean install, it would ask the operator if
they want a new callsign certificate request. That message now explains
that if the operator is planning to restore from a backup, then requesting
a new certificate is the wrong thing to do.

o When restoring a backup, TQSL doesn't restore entries like directory
names when the source operating system (Windows, Mac, Linux) differs from
the target.

o When updating station location details from an ADIF file, TQSL now
verifies the format and consistency of the data - previously, TQSL assumed
that the data was correct as emitted by the logging program.

o The 'Year' dropdown menu on callsign certificate requests starts from
current and goes backwards, placing recent years near the top.

o When an ADIF file contained an invalid DXCC entity number, TQSL would
crash, This now results in an error message.

o When an ADIF file contained an invalid US_STATE such as "CONFUSED", TQSL
was matching on only the first two letters, allowing this to pass as
Colorado.  TQSL now requires the proper two-character state abbreviation
(along with accepting full state names such as "Colorado" for cases where
loggers emit non-conforming ADIF.

o When loading a P12 file from the command line, where the password given
was incorrect, TQSL would display an error message and then wait for the
user to click "ok".  It has been corrected to exit for these cases.

o TQSL now permits 12-character gridsquares.

Lots of changes, some minor and some major.
Any testing and feedback you can provide is welcome and appreciated!

Update kits:
https://www.rickmurphy.net/lotw/tqsl-2.8.msi - Windows
https://www.rickmurphy.net/lotw/tqsl-2.8.pkg - Mac, 64-bit
https://www.rickmurphy.net/lotw/tqsl-legacy-2.8.pkg - Mac, 32-bit
https://www.rickmurphy.net/lotw/tqsl-2.8.tar.gz - Linux/BSD

73,
    -Rick
-- 
Rick Murphy, D.Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

[Trustedqsl-testing] TQSL 2.7.4 Release candidate available

[Rick M. <k1...@ar...>]

Announcing the TQSL 2.7.4-rc3 release candidate.
Any testing to validate that there's no regressions or bugs introduced
would be appreciated.
Major changes for this release:
o TQSL warns users submitting portable callsign requests using a US base
callsign that operations such as CEPT, IARP, or other reciprocity
agreements are only available to US citizens.

o TQSL on Linux would send out a number of 'Gtk-WARNING' messages due to
GUI layout issues. These weren't causing the application to fail, but they
were annoying. TQSL has those issues fixed.

o Attempts to request callsign certificates for US callsigns where the FCC
address data had empty fields such as the address could cause TQSL to lock
up and not respond. TQSL now allows the user to fill in the missing details.

o TQSL now has a Gridsquare data set that operates at the DXCC entity and
primary administrative subdivision (State, Province, etc.) level. This
allows validation that at least the four character grid is appropriate for
the entity and state.

o TQSL would allow a user to save an invalid Gridsquare by pressing "Next"
repeatedly. This is no longer allowed.

o Language selection for Chinese variants was not working properly due to a
change in the wxWidgets components that manage the TQSL GUI.  TQSL has a
workaround to allow stable language selection.

o When a station location is edited, including when details such as state
were set from external data, TQSL now warns the user that some fields have
been changed and asks if it's OK to discard those.  This warning message
was in place for TQSL 2.7.3 but could display garbled field names, which is
now corrected.

o Cases where network connectivity to ARRL is impaired are now detected
more quickly and don't lock TQSL up for extended periods of time.

o TQSL now allows recently expired Callsign Certificates to be renewed.

o If upload of a Callsign Certificate request to ARRL fails due to network
issues, TQSL now allows the user to save that request for later upload.

o The command line signing configuration now allows an empty station
location name to be specified. In this case, each QSO is required to
provide MY_xxxx ADIF fields to specify the QTH details and callsign to use.

Kits available from:
https://www.rickmurphy.net/lotw/tqsl-2.7.4.msi  - Windows
https://www.rickmurphy.net/lotw/tqsl-2.7.4.pkg  - Mac
https://www.rickmurphy.net/lotw/tqsl-legacy-2.7.4.pkg - 32-Bit Mac
(Intel/PPC)
https://www.rickmurphy.net/lotw/tqsl-2.7.4.tar.gz  - Linux, BSD, etc.

73,
    -Rick




-- 
Rick Murphy, D.Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

[Trustedqsl-testing] TQSL 2.7.3 Release candidate

[Rick M. <k1...@ar...>]

I'm preparing to release a new version of TQSL.
The primary change here is to clean up TQSL's display of callsign
certificates (removing the 'awaiting ARRL' message), detect attempts to
install old (expired, replaced) TQ6 files, while pointing users to how to
get their current callsign certificate from Logbook. TQSL also tries to
detect cases where the user's date is set wrong and provide guidance.

There's a minor change to allow a user to export callsign certificates
using weak, obsolete cryptographic algorithms necessary to allow import
into the Apple keyring,

https://www.rickmurphy.net/lotw/tqsl-2.7.3.msi                Windows
https://www.rickmurphy.net/lotw/tqsl-2.7.3.pkg                Mac
https://www.rickmurphy.net/lotw/tqsl-2.7.3.tar.gz             Unix/Linux
https://www.rickmurphy.net/lotw/tqsl-legacy-2.7.3.pkg    Mac, 32-bit

Please give this a spin. Any input is welcome!
73,
    -Rick
-- 
Rick Murphy, D.Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: [Trustedqsl-testing] TQSL 2.7 beta2 now available

[Richard S. <hob...@gm...>]

On Mon, Sep 18, 2023 at 6:33 AM Rick Murphy <k1m...@gm...> wrote:

> The cause here is that the data being returned by the upload database
> query is getting overwritten by sqlite so TQSL sees random garbage.
> Fixed by making a copy of the data and managing release of that so it
> sticks around until I need it.
> Since you're building from source, patch attached. This will of course be
> fixed in the release candidate,
>
> Thanks for discovering this!
>

I can confirm it works for me. Thanks!

Richard
KF5OIM

Re: [Trustedqsl-testing] TQSL 2.7 beta2 now available

[Rick M. <k1m...@gm...>]

The cause here is that the data being returned by the upload database query
is getting overwritten by sqlite so TQSL sees random garbage.
Fixed by making a copy of the data and managing release of that so it
sticks around until I need it.
Since you're building from source, patch attached. This will of course be
fixed in the release candidate,

Thanks for discovering this!
73,
    -Rick

On Sun, Sep 17, 2023 at 10:36 PM Rick Murphy <k1m...@gm...> wrote:

> On Sun, Sep 17, 2023 at 10:14 PM Richard Shaw <hob...@gm...>
> wrote:
>
>> On Sun, Sep 17, 2023 at 8:10 AM Rick Murphy <k1m...@gm...>
>> wrote:
>>
>>> I'd have a look at your upload logs on Logbook - are you seeing
>>> previously uploaded QSOs showing up?
>>>
>>
>> I didn't see any duplicates or anything
>>
>
> Then nothing got re-uploaded.  Seems strange. But - see below. There is
> something wrong here.
>
>
>> ...
>>
>>> What platform are you using?
>>>
>>
>> Fedora Linux 38. I've been the package maintainer for several years now.
>>
>
> That makes it easy. I develop on Fedora and move to the other platforms.
> Currently I'm running F38.
> I just tried this and saw the same thing: signing a log with mostly
> uploaded QSOs and they just went through.
> I'll dig in as to why - this isn't intended.
> 73,
>     -Rick
> --
> Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA
>


-- 
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: [Trustedqsl-testing] TQSL 2.7 beta2 now available

[Rick M. <k1m...@gm...>]

On Sun, Sep 17, 2023 at 10:14 PM Richard Shaw <hob...@gm...> wrote:

> On Sun, Sep 17, 2023 at 8:10 AM Rick Murphy <k1m...@gm...> wrote:
>
>> I'd have a look at your upload logs on Logbook - are you seeing
>> previously uploaded QSOs showing up?
>>
>
> I didn't see any duplicates or anything
>

Then nothing got re-uploaded.  Seems strange. But - see below. There is
something wrong here.


> ...
>
>> What platform are you using?
>>
>
> Fedora Linux 38. I've been the package maintainer for several years now.
>

That makes it easy. I develop on Fedora and move to the other platforms.
Currently I'm running F38.
I just tried this and saw the same thing: signing a log with mostly
uploaded QSOs and they just went through.
I'll dig in as to why - this isn't intended.
73,
    -Rick
-- 
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: [Trustedqsl-testing] TQSL 2.7 beta2 now available

[Richard S. <hob...@gm...>]

On Sun, Sep 17, 2023 at 8:10 AM Rick Murphy <k1m...@gm...> wrote:

> I'd have a look at your upload logs on Logbook - are you seeing previously
> uploaded QSOs showing up?
>

I didn't see any duplicates or anything


> Note that this practice - upload everything and let the software filter
> the new ones - is strongly discouraged.
>

Hence my concern, it's always filtered the duplicates before now.



> The upload data kept by TQSL is per-computer so QSOs uploaded from one
> computer won't be recorded on any others (unless you backup the first and
> restore the TBK to the others.)
>

I only keep a log on my desktop. If I do happen to work from my laptop I
copy the ADIF files over.


What platform are you using?
>

Fedora Linux 38. I've been the package maintainer for several years now.

Thanks,
Richard
KF5OIM

Re: [Trustedqsl-testing] TQSL 2.7 beta2 now available

[Rick M. <k1m...@gm...>]

I'd have a look at your upload logs on Logbook - are you seeing previously
uploaded QSOs showing up?

Note that this practice - upload everything and let the software filter the
new ones - is strongly discouraged.
The upload data kept by TQSL is per-computer so QSOs uploaded from one
computer won't be recorded on any others (unless you backup the first and
restore the TBK to the others.)

What platform are you using?
73,
    -Rick

On Sun, Sep 17, 2023 at 8:31 AM Richard Shaw <hob...@gm...> wrote:

> On Tue, Sep 12, 2023 at 2:15 PM Rick Murphy <k1m...@gm...> wrote:
>
>> I've just tried this and got the expected "This log contains x QSO(s)
>> which appear to have already been signed for upload to LoTW.." dialog.
>> 73
>>
>
> Interesting, I tried a second time and for me it was the same as the
> first, no prompt...
>
> Thanks,
> Richard
> KF5OIM
> _______________________________________________
> Trustedqsl-testing mailing list
> Tru...@li...
> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>


-- 
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: [Trustedqsl-testing] TQSL 2.7 beta2 now available

[Richard S. <hob...@gm...>]

On Tue, Sep 12, 2023 at 2:15 PM Rick Murphy <k1m...@gm...> wrote:

> I've just tried this and got the expected "This log contains x QSO(s)
> which appear to have already been signed for upload to LoTW.." dialog.
> 73
>

Interesting, I tried a second time and for me it was the same as the first,
no prompt...

Thanks,
Richard
KF5OIM

Re: [Trustedqsl-testing] TQSL 2.7 beta2 now available

[Rick M. <k1m...@gm...>]

I've just tried this and got the expected "This log contains x QSO(s) which
appear to have already been signed for upload to LoTW.." dialog.
73,
    -Rick

On Tue, Sep 12, 2023 at 8:33 AM Rick Murphy <k1m...@gm...> wrote:

> Thanks. I'll have a look.
> 73,
>     -Rick
>
> On Tue, Sep 12, 2023 at 7:45 AM Richard Shaw <hob...@gm...> wrote:
>
>> On Tue, Sep 12, 2023 at 6:44 AM Richard Shaw <hob...@gm...>
>> wrote:
>>
>>> On Mon, Sep 11, 2023 at 10:18 PM Rick Murphy <k1m...@gm...>
>>> wrote:
>>>
>>>> The first time you run v2.7 it's going to discard the uploaded QSO
>>>> history.
>>>> If you have an automatic backup enabled (File/Display or Modify
>>>> Preferences) and a good backup exists, then that data should be restored.
>>>> Is that consistent, or is there something else going on that I need to
>>>> investigate?
>>>>
>>>
>>> Maybe I didn't explain it very quickly. Just as a test of the new
>>> version I did the usual first option in TQSL, sign and upload.
>>>
>>
>> correctly... Sorry still working on coffee #1 this morning.
>>
>>>
>>> On one of the pop-ups it asks for a date range to include which I never
>>> use. Once I click OK previously it would tell me I have XXX number of
>>> duplicates and XXX new contacts but this did not happen.
>>>
>>> Logging into the site I don't see duplicates or anything I just didn't
>>> know if it automatically skipped duplicates or re-processed all of my
>>> contacts.
>>>
>>> Thanks,
>>> Richard
>>> KF5OIM
>>>
>> _______________________________________________
>> Trustedqsl-testing mailing list
>> Tru...@li...
>> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>>
>
>
> --
> Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA
>


-- 
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: [Trustedqsl-testing] TQSL 2.7 beta2 now available

[Rick M. <k1m...@gm...>]

Thanks. I'll have a look.
73,
    -Rick

On Tue, Sep 12, 2023 at 7:45 AM Richard Shaw <hob...@gm...> wrote:

> On Tue, Sep 12, 2023 at 6:44 AM Richard Shaw <hob...@gm...> wrote:
>
>> On Mon, Sep 11, 2023 at 10:18 PM Rick Murphy <k1m...@gm...>
>> wrote:
>>
>>> The first time you run v2.7 it's going to discard the uploaded QSO
>>> history.
>>> If you have an automatic backup enabled (File/Display or Modify
>>> Preferences) and a good backup exists, then that data should be restored.
>>> Is that consistent, or is there something else going on that I need to
>>> investigate?
>>>
>>
>> Maybe I didn't explain it very quickly. Just as a test of the new version
>> I did the usual first option in TQSL, sign and upload.
>>
>
> correctly... Sorry still working on coffee #1 this morning.
>
>>
>> On one of the pop-ups it asks for a date range to include which I never
>> use. Once I click OK previously it would tell me I have XXX number of
>> duplicates and XXX new contacts but this did not happen.
>>
>> Logging into the site I don't see duplicates or anything I just didn't
>> know if it automatically skipped duplicates or re-processed all of my
>> contacts.
>>
>> Thanks,
>> Richard
>> KF5OIM
>>
> _______________________________________________
> Trustedqsl-testing mailing list
> Tru...@li...
> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>


-- 
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: [Trustedqsl-testing] TQSL 2.7 beta2 now available

[Richard S. <hob...@gm...>]

On Tue, Sep 12, 2023 at 6:44 AM Richard Shaw <hob...@gm...> wrote:

> On Mon, Sep 11, 2023 at 10:18 PM Rick Murphy <k1m...@gm...>
> wrote:
>
>> The first time you run v2.7 it's going to discard the uploaded QSO
>> history.
>> If you have an automatic backup enabled (File/Display or Modify
>> Preferences) and a good backup exists, then that data should be restored.
>> Is that consistent, or is there something else going on that I need to
>> investigate?
>>
>
> Maybe I didn't explain it very quickly. Just as a test of the new version
> I did the usual first option in TQSL, sign and upload.
>

correctly... Sorry still working on coffee #1 this morning.

>
> On one of the pop-ups it asks for a date range to include which I never
> use. Once I click OK previously it would tell me I have XXX number of
> duplicates and XXX new contacts but this did not happen.
>
> Logging into the site I don't see duplicates or anything I just didn't
> know if it automatically skipped duplicates or re-processed all of my
> contacts.
>
> Thanks,
> Richard
> KF5OIM
>

Re: [Trustedqsl-testing] TQSL 2.7 beta2 now available

[Richard S. <hob...@gm...>]

On Mon, Sep 11, 2023 at 10:18 PM Rick Murphy <k1m...@gm...> wrote:

> The first time you run v2.7 it's going to discard the uploaded QSO history.
> If you have an automatic backup enabled (File/Display or Modify
> Preferences) and a good backup exists, then that data should be restored.
> Is that consistent, or is there something else going on that I need to
> investigate?
>

Maybe I didn't explain it very quickly. Just as a test of the new version I
did the usual first option in TQSL, sign and upload.

On one of the pop-ups it asks for a date range to include which I never
use. Once I click OK previously it would tell me I have XXX number of
duplicates and XXX new contacts but this did not happen.

Logging into the site I don't see duplicates or anything I just didn't know
if it automatically skipped duplicates or re-processed all of my contacts.

Thanks,
Richard
KF5OIM

Re: [Trustedqsl-testing] TQSL 2.7 beta2 now available

[Rick M. <k1m...@gm...>]

The first time you run v2.7 it's going to discard the uploaded QSO history.
If you have an automatic backup enabled (File/Display or Modify
Preferences) and a good backup exists, then that data should be restored.
Is that consistent, or is there something else going on that I need to
investigate?
73,
    -Rick


On Mon, Sep 11, 2023 at 10:29 PM Richard Shaw <hob...@gm...> wrote:

> I built a test package for Fedora and was able to upload my WSJT-X
> contacts.
>
> I noticed that usually I just upload everything and let it remove the
> duplicates for me. In this case it did not ask. Is that expected?
>
> Thanks,
> Richard
> KF5OIM
> _______________________________________________
> Trustedqsl-testing mailing list
> Tru...@li...
> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>


-- 
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: [Trustedqsl-testing] TQSL 2.7 beta2 now available

[Richard S. <hob...@gm...>]

I built a test package for Fedora and was able to upload my WSJT-X contacts.

I noticed that usually I just upload everything and let it remove the
duplicates for me. In this case it did not ask. Is that expected?

Thanks,
Richard
KF5OIM

[Trustedqsl-testing] TQSL 2.7 beta2 now available

[Rick M. <k1...@ar...>]

I've been putting off release of 2.7 but there's now enough changes to push
this over the wall.

2.7beta2 has several improvements;
- The uploads database is updated from Oracle' Berkeley DB because the
Oracle database is simply unusable, repeatedly corrupting the database for
no reason.
Since Oracle's database is fragile and breaks a lot, I've replaced the
uploads database with SQLite. Hopefully this will eliminate the frequent
database corruption.
- Fixes for 1x1 callsign handling to stop validating against the FCC ULS
database when an end-date is provided.
- Allow OPERATOR in ADIF files to be longer than a normal callsign. If the
OPERATOR is incorrectly set to the name of the operator, then it's not a
callsign and will be ignored.
- Update portable callsign handling. This now allows prefix/call like
MU/K1MU and handles it properly.
- Add a preference to allow callsigns in ADIF files to be ignored when
signing.
- Fix portable call handling for non-US stations "P5ROMEO/W4" used to
require a US base call.
- Restore the uploaded QSO database from the last backup when it gets
corrupted.

The other major change here is to build a "flatpak" image for Linux
distributions.
This allows install on most 64-bit Linux systems with no compiling needed.
I just installed the latest Flatpak build on a Chromebook and a Raspberry
Pi - easy peasy,

Mac 64-bit builds now work on Apple Silicon (M1/M2 currently) systems.
Mac 32-bit builds work on PPC and Intel i386.
(Is anyone actually using the 32-bit Mac builds?)

Kits:
Windows: https://www.rickmurphy.net/lotw/tqsl-2.7.msi
Mac, 64-bit: https://www.rickmurphy.net/tqsl-2.7.pkg
Mac, 32-bit: https://www.rickmuphy.net/tqsl/tqsl-legacy-2.7.pkg
Unix source: https://www.rickmurphy.net/tqsl/tqsl-2.7.tar.gz

Linux Flatpak: https://flathub.org/apps/org.arrl.trustedqsl

I'm very interested in upload testing due to the uploads database changes,
and feedback on the Flatpak builds for Linux as that took a lot of work to
get accepted in their repository.
73,
    -Rick
-- 
Rick Murphy, D.Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

[Trustedqsl-testing] TQSL 2.7 beta version available for testing

[Rick M. <k1...@ar...>]

A new release of TQSL (2.7) is in progress.  Beta versions of this release
are now available for testing; these have all of the major changes expected
for 2.7.

Changes:
1. When the "uploads" database gets corrupted or is missing, try to recover
it from a backup. In the past, TQSL would start over with an empty
database, losing all upload history. The fact that TQSL by default performs
an automatic backup when it's run means that a good source of upload data
is often available.

2. Change the upload database from Oracle BerkeleyDB (BDB) to Lightning
Memory-Mapped Database (LMDB). This removes a source of frequent errors
because that database was getting corrupted, with many attempts to
repair/recover by TQSL not working as hoped.  LMDB has higher performance
and does not have the licensing issues found with BDB.

3. Upgrade the Mac kits to support native Apple Silicon (arm64) and Intel
64-bit; the legacy kit is now only for 32-bit Intel and PowerPC.  Some
components of TQSL are lagging behind with this release as they will not
build on these older systems. Input on the value of continuing to maintain
the 32-bit Mac systems is of value.

Please give these a spin. All feedback is gratefully accepted. This will go
to a release candidate once the translator updates are completed, which
probably means early December.

Kits:
https://www.rickmurphy.net/lotw/tqsl-2.7.msi - Windows
https://www.rickmurphy.net/lotw/tqsl-2.7.pkg - Mac 64-bit
https://www.rickmurphy.net/lotw/tqsl-legacy-2.7.pkg - Mac 32-bit
https://www.rickmurphy.net/lotw/tqsl-2.7.tar.gz - Linux/BSD source
https:/www.rickmurphy.net/lotw/tqsl-2.7_x86_64.AppImage - Linux pre-built

73,
    -Rick
-- 
Rick Murphy, D.Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

[Trustedqsl-testing] RC released publicly

[Björn E. <bj...@ek...>]

Was the public release of 2.6.5 rc4 really intentional?

Wouldn't it be better to wait until there is a final one?

Now TQSL tells you there is a new release over and over and over again...

Björn SM7IUN