Re: [Trustedqsl-testing] Beta version of TQSL available for testing

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

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