Up to [cvs.NetBSD.org] / pkgsrc / ham / trustedQSL
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
(ham/trustedQSL) Updated 2.7.5 to 2.8 https://www.arrl.org/files/file/LoTW%20Instructions/TrustedQSL-2-8-release.pdf Trusted QSL V2.8 Release Notes This version of Trusted QSL (TQSL) has new features as well as corrections for defects found since TQSL 2.7 was released. Updates since TQSL 2.7.5 This release includes an update to the most recent TQSL configuration file. There were no serious defects reported for TQSL 2.7.5. This release contains several minor updates which have accumulated since 2.7 was released. TQSL 2.8 can be installed to upgrade any older version of TQSL. For the Mac platform, TQSL now uses a package file (.pkg) for installing TQSL. This is hopefully easier to use as it is a familiar way to install software for most Mac users. Mac users may have previously installed TQSL into "a/Applications/tqsl.app" versus the "/Applications/TrustedQSL/tqsl.app" folder (which is the proper location based on Apple guidance.) If you have installed TQSL into /Applications/tqsl.app, you should delete this by dragging that file to the trash. If you don't do that, TQSL will repeatedly offer to upgrade. The "tqsl-legacy" packages run on 32-bit Intel and PowerPC processors and require Mac OS 10.5 or later. The non-legacy packages for the Mac require Mac OS 10.10 or later and support 64-bit Intel and Apple Silicon processors. On all three supported platforms (Windows, MacOS, and Linux), installing TQSL 2.8 will replace older versions of Trusted QSL while preserving your Callsign Certificates, Station Locations, and preferences. On Windows, simply run the TQSL 2.8 installer, which will automatically uninstall older versions of TQSL (and, if installed, TQSLCert). On Mac OS X, open the package (.pkg) file to install TQSL into your Applications folder. If you have previously installed TQSL into some other folder, you may need to delete that folder to allow the new version to operate properly. For Linux systems, I recommend using the copy on Flathub: https://flathub.org/apps/org.arrl.trustedqsl - That is a portable Linux package that will run on many 64-bit Linux systems (x86_64 and ARM64). If you need to build from source, unpack the tar file and read the INSTALL file for directions. You will need development libraries for zlib, curl, openssl, sqlite3, wxWidgets, and expat. TQSL 2.8 has been "localized" to allow use in the native language of non-English speakers. This could not have been done without the help of the volunteers who have contributed translations for TQSL. Thanks to the following for their assistance: Catalan: Xavier, EA3W Chinese (Simplified): SZE-To, VR2UPU Chinese (Traditional): Caros, BH4TXN Finnish: Juhani, OH8MXL French: Laurent BEUGNET, F6GOX Hindi: Manmohan, VU3YBH German: Andreas, DF4WC Italian: Salvatore, IV4FYV Japanese: Akihiro, JL3OXR Portuguese: Nuno, CT2IRY Russian: Vic, US5WE Spanish: Jordi, EA3GCV Swedish: Roger, SM0LTV Turkish: Ojuzhan, TA2NC The following list describes the major changes in the v2.8 release of Trusted QSL. TQSL changes Defects Corrected: When creating a station location, entering a gridsquare that was incorrect for the primary administrative subdivision (state, province, etc.) was not flagged as an error. This correction ensures that for this case, the incorrect grid is flagged as an error. TQSL would crash while signing a log that contained an invalid or out-of-range value for the ADIF MY_DXCC tag. TQSL now reports this as an invalid value. When signing a log, TQSL would allow a log containing incorrect or inconsistent values for MY_ ADIF fields such as MY_GRIDQUARE, MY_STATE, MY_COUNTY, and MY_IOTA. TQSL now properly evaluates ADIF data to ensure that things like a grid from outside of the entity and state (province, etc.) are rejected. When signing a log with the ADIF MY_IOTA tag present, TQSL would emit an error claiming that the data was incorrect when it was properly formatted. TQSL now properly validates this tag. Input from ADIF logs could have poorly formatted or incorrect data that TQSL would not detect. For example, the MY_STATE tag (which is supposed to have the two letter abbreviation for the state) allowed a user to specify "CONFUSED", which would match the two-letter abbreviation (CO) for Colorado. Or, a value of "New York" to be treated as Nebraska. TQSL now requires the entire field string to be correct. When signing a log in "update" mode, gridsquare settings from MY_GRIDSQUARE or MY_VUCC_GRIDS were not being used to update the active station location. These are now properly being applied to the QSO being signed. Major feature Additions: A new "Help" menu item, "Synchronize upload data with LoTW.." allows you to download all of your QSOs from Logbook and add them to the "already uploaded QSOs" database managed by TQSL. This ensures that this data is complete and consistent with Logbook. This can allow you to recover from a computer crash, and to filter log uploads with assurance that your data and LoTW's are the same. Minor Updates: When signing a log while other signing actions are in progress, TQSL could display a "Database is locked" error as well as "Application is not responding" messages. TQSL now displays more information about the conflicting operations and directs the user on how to resolve the issue. The callsign certificate request process has had several usability improvements: 1. TQSL now provides more detail and better guidance about when signing is needed. This removes a bunch of jargon that made it hard to understand what was being asked. 2. When selecting the date range for a Callsign Certificate request, the years are now ordered in descending order, not starting with 1945 - this means less scrolling to get to Y2K. 3. When requesting a callsign certificate, the entities displayed are filtered using the prefix of the given callsign. This means much less scrolling to select an entity, and helps to ensure that the right entity is chosen. (There is a checkbox to allow any entity to be chosen.) Gridsquares in an ADIF file MY_GRIDSQUARE tag is allowed to up to 12 characters long. This is not strictly correct ADIF, but Logbook does support this usage. MY_VUCC_GRIDS remains limited to 6character grids. The command line "-I" switch now allows import of a backup (.tbk) file in addition to importing callsign certificates. The TQSL wording of "already uploaded" has been changed to "previously signed". This removes the implied assumption that signing a log means that it has been updated. A new "Test Signing an ADIF or Cabrillo file" menu option has been added. This signs a log, but does not store those QSOs in the uploads database. It also produces an uncompressed TQ7 file. When restoring configuration data from a TBK file, certain preferences which point to folder locations are not restored, as those could refer to folders that do not exist on the target system. This avoids Windows folder names being restored on a Mac. When loading a P12 file on the command line "-I" switch, for cases where the passphrase given was incorrect, TQSL would display the GUI and show an error message. This did not allow automated operations to detect the incorrect password. TQSL now exits to allow the application to ask the user for the proper passphrase. The Chinese localizations were not working on a Mac computer due to a change to the underlying GUI code (wxWidgets). These now operate properly. Reinstalling TQSL 2.7.x Downgrading to TQSL 2.7.5 can be seamlessly performed by uninstalling TQSL 2.8 and reinstalling TQSL 2.7.5.
(ham/trustedQSL) Updated 2.7.3 to 2.7.5 https://www.arrl.org/files/file/LoTW%20Instructions/TrustedQSL-2-7-5-release.pdf Defects Corrected: [2.7.5] Renewing a callsign certificate which had not expired was blocked (the menus were greyed out) unless the certificate had actually expired. TQSL 2.7.5 allows renewal of certificates which have not expired. When updating QTH details from an ADIF log, certain fields such as US_STATE were not upper-cased as expected by Logbook of the World. This could result in credit for more than 50 US States on LoTW. TQSL 2.7.5 now properly uppercases those fields Defects Corrected: [2.7.4] Further correction of handling of US portable callsigns and FCC Universal Licensing Service (ULS) data. Callsigns with blank fields in the ULS data, or with PO boxes for addresses, would cause TQSL to lock up and not allow submitting callsign certificate requests. Correct handling of language mapping. Changes to the underlying wxWidgets platform caused some translations to fail. When editing or creating Station Locations, saving of invalid gridsquares is now rejected. TQSL would allow a user to repeatedly click “next” to bypass the check Major feature Additions: [2.7.4] TQSL now has a database of valid gridsquares indexed by DXCC entity and primary subdivision (state, province, etc.) allowing detection of invalid gridsquares in station locations. When upload of a Callsign Certificate request fails, TQSL now allows the user to save that for a later upload. Handle network outages more graciously. Don't repeatedly try to connect to Logbook when it's down, as this could cause startup to take many minutes for some circumstances. TQSL now detects the errors and stops trying. Minor Updates: [2.7.4] Allow renewal of Callsign Certificates that expired within the last 90 days. Warn users with US base callsigns and portable modifiers that reciprocity agreements such as CEPT require US callsign holders to be US citizens. Suppress "wxGTK-WARNING" messages on Linux systems. Allow an empty location name on the command line to indicate to TQSL that the log submitted for signing has valid station location data (ADIF MY_xxx fields) and that no station location should be used.
(ham/trustedQSL) Updated 2.6.5 to 2.7.3 Release note may be found at: http://www.arrl.org/files/file/LoTW%20Instructions/TrustedQSL-2-7-3-release.pdf
(ham/trustedQSL) Updated 2.5.8 to 2.6.3 Release note for 2.6.3 wil be found at http://www.arrl.org/files/file/LoTW%20Instructions/TrustedQSL-2-6-3-release.pdf [2.6.1] This release includes an update to correct a defect that could cause TQSL to "hang" and never complete signing a log when previously submitted QSOs were submitted for signing. [2.6.2] Several minor usability updates were implemented. See details below. TQSL 2.6.3 can be installed to upgrade any older version of TQSL.
trustedQSL: Update to 2.5.7 This is basically a bugfix release. Some patches are overtaken by upstream events.
Upgraded ham/trustedQSL to 2.4.2 Trusted QSL V2.4.2 Release Notes This version of Trusted QSL (TQSL) has new features as well as corrections for defects found since TQSL 2.4.1 was released. This release also includes an update to the most recent TQSL configuration file. TQSL 2.4.2 can be installed to upgrade any older version of TQSL. You do not need to install every release from 2.2 through 2.4, you can upgrade directly to v2.4.2 in one step. IMPORTANT NOTE for MacOS users: TQSL has been built to be compatible with older Mac systems (OSX 10.4 and later) and to work on both PowerPC and Intel CPU Macs. The current release of OSX (10.14, or Mojave) issues a warning about TQSL when it is run stating that it is not “optimized”, and that it will not work with the next release of OSX. This is forcing us to drop support for PowerPC systems in order to continue to support Mac systems. We will freeze TQSL 2.4.x and make it available indefinitely, but the next major release of TQSL will not work on PowerPC Macs or Macs running OSX older than Tiger. On all three supported platforms (Windows, MacOS, and Linux), installing TQSL 2.4.2 will replace older versions of Trusted QSL while preserving your Callsign Certificates, Station Locations, and preferences. On Windows, simply run the TQSL 2.4.2 installer, which will automatically uninstall older versions of TQSL (and, if installed, TQSLCert). On Mac OS X, open the disk image (.dmg) file and drag the “Trusted QSL” folder to your Applications folder. Direct the installer to “Replace All”, which will uninstall old files. For Linux systems, unpack the tar file and read the INSTALL file for directions. TQSL 2.4.2 has been “localized” to allow use in the native language of non-English speakers. This could not have been done without the help of the volunteers who have contributed translations for TQSL. Thanks to the following for their assistance: Chinese: Caros, BH4TXN Hindi: Manmohan, VU3YBH German: Andreas DF4WC Italian: Salvatore IV4FYV Japanese: Akihiro JL3OXR Portuguese: Nuno CT2IRY Russian: Vic US5WE Spanish: Jordi EA3GCV The following list describes the major changes in the v2.4.2 release of Trusted QSL. TQSL changes Defects Corrected: Ensure that the exit status message emitted by TQSL appears in English so logging programs can use that to detect exit status. In the past, this could have been output in the local language, making it more difficult for the calling program to detect whether or not there were any errors. Improve setting of ITU and CQ zones when defining a Station Location. There were many cases where these were left empty, which means that Station Locations were more likely to not have zones defined. Fix issue with Windows updates of TQSL failing when the user's directory has a space embedded. Note that this is a forwards-looking fix: this defect is in the existing TQSL 2.4.1, so updates for users with spaces in their usernames will continue to fail until after 2.4.2 is installed. Remove spurious error message when run on a system where the local language is not supported. Features Added: When displaying a callsign certificate where the private key is missing from the local system, specifically state that the private key is not found. Added a specific message for keys that cannot be opened to provide the root cause. Improve the error message for missing private keys to be more descriptive. Add the ability to map Cabrillo modes to user-specified ADIF modes using the cab_modes.dat file in the TQSL user directory. File has Cabrillo modes (two characters), then an ADIF mode, comma delimited. Default file is provided by TQSL and users can provide their own. Allow adding translations without making code changes. Reinstalling TQSL 2.4.1 Downgrading to TQSL 2.4.1 can be seamlessly performed by uninstalling TQSL 2.4.2 and reinstalling TQSL 2.4.1.
Updated ham/trusted-QSL (tqsl) to 2.3.1 Trusted QSL V2.3.1 Release Notes This version of Trusted QSL (TQSL) has new features as well as corrections for defects found since TQSL 2.3 was released. This release also includes an update to the most recent TQSL configuration file. TQSL 2.3.1 can be installed to upgrade any older version of TQSL. On all three supported platforms (Windows, MacOS, and Linux), installing TQSL 2.3.1 will replace older versions of Trusted QSL while preserving your Callsign Certificates, Station Locations, and preferences. On Windows, simply run the TQSL 2.3.1 installer, which will automatically uninstall older versions of TQSL (and, if installed, TQSLCert). On Mac OS X, open the disk image (.dmg) file and drag the “Trusted QSL” folder to your Applications folder. Direct the installer to “Replace All”, which will uninstall old files. For Linux systems, unpack the tar file and read the INSTALL file for directions. TQSL 2.3 has been “localized” to allow use in the native language of non-English speakers. This could not have been done without the help of the volunteers who have contributed translations for TQSL. Thanks to the following for their assistance: Chinese: Caros, BH4TXN Finnish: Juhani, OH8MXL German: Andreas DF4WC Italian: Salvatore IV4FYV Japanese: Akihiro JL3OXR Portuguese: Nuno CT2IRY Russian: Vic US5WE Spanish: Jordi EA3GCV The following list describes the major changes in the v2.3.1 release of Trusted QSL. TQSL changes Defects Corrected: - Added 'Saving QSOs' to the messages to be translated. - When renewing a callsign certificate and backing up to earlier pages in the wizard, TQSL could display an unexpected page for selecting the certificate type, which is not needed for renewals. TQSL will no longer display the unexpected page. - When editing an ADIF file that has an invalid mode setting, TQSL now notifies the user that the mode is being ignored. - For Unix systems, fix a defect that could cause the password prompt to not appear when the system has built the wxWidgets system with debug assertions enabled. - Correct the invocation of the Windows Installer when an update is available. - Correct the counts reported when duplicate QSOs are found along with QSOs with other errors. - Fix formatting of the messages that appear when QSOs change values in the station location for duplicate QSOs. - Correct improperly formatted frequencies from ADIF files (values like '7.010.20') to remove the extra periods. - Revert the change that stripped spaces in the TQSL configuration file as that caused newlines to be removed in places like the station_data file. - Fix "OpenSSL error - bad end line" by ensuring that there's always a newline starting a new certificate. Feature Additions: - Add Finnish translation from Juhani, OH8MXL. - Add the ADIF satellite name to the pulldown menu in the ADIF editor to allow satellites to be more easily looked up. - Allow 'LIGHT' in a Cabrillo file to represent 300 GHz and above. - Allow TQSL to build against OpenSSL 1.1.0. - Add the ability to pull DXCC Entity valid date ranges from the TQSL configuration file. Reinstalling TQSL 2.3 Downgrading to TQSL 2.3 can be seamlessly performed by uninstalling TQSL 2.3.1 and reinstalling TQSL 2.3.
Update 2.1.3 to 2.2.1 (tested both with wxGTK28 and wxGTK30) ----------------------------------------------------------------- Following is not for explicit 2.2.1 release but for 2.2, (attached to mail from Rick Murphy on 2015/12/31 as Subject: TrustedQSL 2.2 final release is available for download) ----------------------------------------------------------------- Trusted QSL V2.2 Release Notes This version of Trusted QSL (TQSL) has corrections for defects found since TQSL 2.1 was released (including the updates made for TQSL 2.1.1, 2.1.2, and 2.1.3) as well as improvements to permit TQSL and Logbook of the World to support the National Parks on the Air competition. TQSL 2.2 can be installed to upgrade any older version of TQSL. Downgrade to TQSL 2.1.3 can be seamlessly performed by uninstalling TQSL 2.2 and reinstalling TQSL 2.1.3. On all three supported platforms (Windows, MacOS, and Linux), installing TQSL 2.2 will replace older versions of Trusted QSL while preserving your Callsign Certificates, Station Locations, and preferences. On Windows, simply run the TQSL 2.2 installer, which will automatically uninstall older versions of TQSL (and, if installed, TQSLCert). On Mac OS X, open the disk image (.dmg) file and drag the "Trusted QSL" folder to your Applications folder. Direct the installer to "Replace All", which will uninstall old files. For Linux systems, unpack the tar file and read the INSTALL file for directions. The following list describes the major changes in the v2.2 release of Trusted QSL. TQSL changes Defects Corrected: Fix a defect that could cause saving of Calllsign Certificate private keys to be suppressed. When renewing a Callsign Certificate, entering an invalid password would display an incorrect "Invalid Argument" error versus displaying the proper "Invalid password" error. Under some circumstances, this could cause the related Callsign Certificate to be lost. Accept C7 and 4Y as valid callsign prefixes. When installing a Callsign Certificate fails, display the callsign and serial number to facilitate troubleshooting. When deleting Callsign Certificates and Station Locations, save a copy to allow those to be restored. Reject QSOs that do not specify at least mode, band, date, and time. Correct the TQSL ADIF editor to not use the local decimal point separator for frequencies, as ADIF requires a period(.). Major feature Additions: Use Portuguese (Portugal) translations contributed by Nuno, CT2IRY. Allow multiple dependent fields on a station location screen. This allows both a county and a park entry to be modified when the US state changes for a US Station Location.
(pkgsrc)
- (patch-openssl__cert.cpp)
Add patch to define MAX_PATH macro
- Unable to package with x11/wxGTK30 yet
(upstream)
- Udate 2.0.3 to 2.1.2
-----------
TQSL-2.1.2
The following links are pointers to TrustedQSL (TQSL) V2.1.2, which is
a bug fix for the official TQSL 2.1 release.
Release Notes TrustedQSL-2-1-release.pdf
http://www.rickmurphy.net/lotw/TrustedQSL-2-1-release.pdf
(pkgsrc):
- DEPENDS+= mozilla-rootcerts are removed, cert included now.
- Deleted SUBST_CLASSES+= macro_S to avoid name (_S) conflicts on NetBSD-5.*
(The probelm no longer exists)
- Correct MESSAGE (but this is to be committed separately)
(Upstream): Bump version 2.0 to 2.0.2RC4
---------------
This commit log compiled from that of wip/trustedQSL/Makefile by mef@
Sorry if typo or too compact.
2.0.2RC4 2014/06/07
- No pop up when prompting user for password when batch mode
- If QSO database is corrupted and can not be repaired, delete it
2.0.2RC3 2014/05/09
- Ensure station locations added (sign a log -> list of stn loc.)
- Restore from .tbk to restore multiple pending callsign
certificates for a given callsign
- Correct message when callsign cert. is uploaded
- Delete any older version, when renewed callsign is installed
- Correct the behaviour for non ascii directory name on Windows
- Correct the number of QSO in some case when signing
(ignoring might have shown negative number)
2.0.2RC2 2014/04/22
- Windows only
2.0.2RC1 2014/04/16
- OpenSSL update (Heartbleed). no practical attack anyway
(Windows only)
2.0.1RC9 2014/03/01
- Avoid application crash when database conversion for Open/Close
- Faster conversion of database
2.0.1RC8 2014/02/27
- Limit the number of copies of application running
(multiple run might have database corrution)
2.0.1RC7 2014/02/13
- When a callsign cert is about to expire (within 60 days), TQSL
warns. But even after user submitted renewal, it continued
- Correct the automatic backup directory (by from preference pane)
- Search Log files with .ADI, .ADIF also
2.0.1RC6 2014/02/05
- Copyright notice / date (only)
2.0.1RC5 2014/01/29
- Avoid crash at starting if certifiacate status file is empty
- Corrected for checking for new release even with -RC change
2.0.1RC4 2014/01/22
- Canadian province PQ/QC issue
- Correct start-up threads management
- (OpenSuSE Linux) for pending callsign requests
- Accept valid callsign only based on location
- Correct hang if command line argument is wrong
- Update message during callsign certificate creation
2.0.1RC3, 2014/01/13 (but hangs when reading cert_status.xml)
Two additional changes in TQSL 2.0 RC3:
-------------
A. Because new modes may not yet be specified in ADIF, and because
LoTW may not accept all modes specified in ADIF, TQSL enables you to
"map" a new mode to a mode or mode group recognized by LoTW; this
most often takes the form of mapping a new digital mode to the DATA
mode group. Versions of TQSL prior to 2.0 would allow you to map
modes accepted by LoTW. This version of TQSL will refuse to map a
mode that is accepted by LoTW. Any existing mappings of modes
accepted by LoTW will be automatically removed on startup; you will
be notified if this happens.
B. When submitting log files in Cabrillo format, previous versions of
TQSL submitted FM and PH modes as PHONE. TQSL 2.0 RC2 submits FM mode
as FM, and PH mode as SSB.
----------------------------
2.0.1RC2 2013/09/01
Contest name recognition is corrected (Re: JIDX)
(Upstream)
tqsl-2.0 is released
(pkgsrc)
- Tweaks for release candidate (say DIST_SUBDIR etc) are removed
- DEPENDS+= mozilla-rootcerts are added now. This will avoid the error as:
"Peer certificate cannot be authenticated with given CA certificates"
(SSL certificate problem: self signed certificate in certificate chain)
see also http://curl.haxx.se/docs/sslcerts.html
- Add SUBST_CLASSES+= macro_S to avoid name (_S) conflicts on NetBSD-5.*
- Add MESSAGE for rootcerts and firt thing to do after installaton
Add missing entry of pixmaps icon *.png file. I am afraid this problem can not be detected by pbulk packaging. The PATH for the icon may not be correct, but this is where upstream places it (please correct me if unappropriate, thanks).
Import tqsl-2.0rc3 as ham/trustedQSL. TrustedQSL is a LoTW (Logbook of The World) application to upload QSO's (contacts) information onto Logbook servers maintained by the ARRL (American Radio Relay League). Logbook of The World - LoTW - is an exciting way for Radio Amateurs to confirm two-way contacts they have made and use the confirmations as credit toward various awards. Because Logbook of The World uses double blind comparison, users cannot see what other users have uploaded unless there is a matched QSO.