Upstream changed the lib64 stuff a bit, making our SUBST pattern no
longer match. (Either that, or we just got it wrong.) Adjust
pattern.
Pointed out by rillig@.
Some content was about long-ago breaking changes and is no longer
relevant. Everything else is pointers to docs which are superceded by
the general notion that docs should be read :-)
(after off-list discussion with $MAINTAINER)
Sign/upload of log tested on NetBSD 8 amd64.
Packaging changes:
Change to wxGTK30, and don't use mk/wxGTK.mk
Force off lmdb in tqsl's cmake
Upstream NEWS:
localization
Major feature Additions:
Use an ARRL-supplied web service with ULS data to pre-fill station
location information.
Detect when the user runs TQSL “As Administrator” on Windows
systems and warn that this is not recommended.
The user is allowed to temporarily or permanently ignore that
warning.TQSL no longer asks for passwords for callsign
certificates when they are created.
There is a preference setting to re-enable this if desired.
When submitting requests for US 1x1 callsigns, which must always
be a signed request, ensure that the flow properly marks the
callsign as 1x1, and that the requester has a valid callsign
certificate that can be used to sign that request.
minor updates and bugfixes
While the package is not documented to use C++11, it uses std::string
constructs added in C++11, and fails compilation with g++ 5.5.0
without --std=c++11. Add todo markings to file upstream bugs;
upstream does not adequately document prereqs.
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.
Performing substitutions during post-patch breaks tools such as mkpatches,
making it very difficult to regenerate correct patches after making changes,
and often leading to substituted string replacements being committed.
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.
-----------------------------------------------------------------
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.
---------------
TQSL ChangeLog
https://lotw.arrl.org/lotw-help/tqslchangelog/
2.1.3
Revert change in the behavior for command line
applications. TQSL 2.1 changed the behavior for ADIF files
to open those with the TQSL ADIF editor versus signing
them unless "-x" or "-q" were on the command line.
This was an incompatible change that is not consistent
with the documentation and was removed. Fix defect that
could cause newly imported callsign certificates tobe
deleted after the import completed.
Existing SHA1 digests verified, all found to be the same on the
machine holding the existing distfiles (morden). Existing SHA1
digests retained for now as an audit trail.
- (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
----------------------------
tqsl-2.0.2 to 2.0.3 change:
----------------------------
(tqslilb: 2.4)
Fix defect that doesn't allow adding station locations if only a single
callsign certificate is installed.
(following diff is manually editted, tabs are deleted)
diff -urp tqsl-2.0.2/src/location.cpp tqsl-2.0.3/src/location.cpp
--- tqsl-2.0.2/src/location.cpp 2014-07-13 05:18:13.000000000 +0900
+++ tqsl-2.0.3/src/location.cpp 2014-07-17 10:22:16.000000000 +0900
@@ -1152,6 +1152,9 @@ update_page(int page, TQSL_LOCATION *loc
field.idx = static_cast<int>(field.items.size());
field.items.push_back(item);
}
+ if (field.idx == -1 && field.items.size() == 1) {
+ field.idx = 0;
+ }
if (field.idx >= 0) {
field.cdata = field.items[field.idx].text;
}
----------------------------
tqsl-2.0.2RC5 to 2.0.2 change: (Authors note):
----------------------------
As I've had no comments on the 2.0.2-rc5 beta, I've decided that it's time to release it.
The kits on sourceforge have been updated to the final v2.0.2 release.
https://sourceforge.net/projects/trustedqsl/files/TrustedQSL/v2.0.2/
The README there is the preliminary release notes.
Thanks to everyone for the help with testing and reporting issues.
----------------------------
tqsl-2.0.2RC4 to 2.0.2RC5 change:
----------------------------
This release fixes a pair of related defects that have been there
since TQSL 1.x
When you create a station location, you associate it with a callsign
certificate. When you sign a log, you select a location for signing,
which then uses the callsign to select the right callsign certificate.
The problems happen when you do unexpected things with those
certificates.
If you create a station location for K1MU, then delete all of the
certificates for K1MU, then signing a log would cause an "Invalid
Argument" error. TQSL has been corrected to now display an error that
there are no valid callsign certificates.
Similarly, if you create a station location and then let the
associated callsign certificate to expire, trying to sign using that
location would also give an unhelpful "Invalid Argument" message.
When there were no matching certificates, displaying the properties of
a station location would display an incorrect callsign.
These defects have been corrected in RC5 so that useful error messages
are displayed for these cases.
- 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)
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
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
--- (Upstream announce) ---
Testing of TQSL 2.0 in preparation for a final release revealed a
defect that was introduced at -RC6.
An attempt to limit the disk space consumed by the duplicates database
broke duplicate detection.
I've reverted that change and released updated kits on Sourceforge.
------ (Upstream announce) ----
There are several changes since 2.0-RC6 that are of note and can use
further testing. We are hoping to release this as the final V2.0 next
week.
- Correct defect that would cause TQSL to crash on startup if the
certificate store could not be read
- Display an error to the user if the station location data file or
certificate store cannot be opened
- When adding a Station Location, properly initialize the callsign to
correspond to the selected callsign certificate/location (not the
first call found)
- Fix the Station Location editor to not show duplicated DXCC entities
- Check for an existing valid Callsign Certificate before starting to
sign a log - if not, display an error and abort
- Updates to documentation including certificate acceptance, station
location modifications, and multi-computer scenarios
- Fix defect that caused double-clicking a .TQ6 file to fail
- Update the message in the callsign certificate request window to
better explain when a request should be signed
- Correct the error messages on TQSL update check failures to properly
explain what was going on.
- Increase the TQSL update timer to allow for slow connections
- Update to the current (v2.5) LoTW configuration file
- Strip leading and trailing spaces from IOTA, WPX, etc. Leaving these
causes signature verification to fail
- Bring up the GUI before performing the automatic update check so it
doesn't appear that TQSL has hung on startup.
