| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
----------------------------
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.
|
|
- 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.
|
|
Fix PR pkg/48777
|
|
|
|
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.
|
|
Upstream replaced DISTFILE without renaming the rc sequence.
I will ask upstream anyway.
diff -ur tqsl-2.0-jp-mirror/apps/ChangeLog.txt tqsl-2.0/apps/ChangeLog.txt
--- tqsl-2.0-jp-mirror/apps/ChangeLog.txt 2013-09-22 00:44:59.000000000 +0900
+++ tqsl-2.0/apps/ChangeLog.txt 2013-10-06 00:04:07.000000000 +0900
@@ -205,6 +205,23 @@
Thank you,
|
|
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).
|
|
Proposed at tech-pkg@ and supported by gdt@, thanks.
----------------------
Date: Saturday, September 21, 2013 8:32 PM
Subject: TQSL-2.0-RC6 Public release available
There's a new TQSL beta test release available for download.
This release corrects the following defects discovered since TQSL
2.0-RC5 (as well as severl enhancements).
Strip leading spaces and trailing spaces from station locations passed
on the command line to help correct for common user errors.
Display LoTW errors returned when a callsign certificate request fails
for some reason.
Record multiple outstanding certificate requests and delete the
pending status if the user deletes the corresponding callsign
certificate.
Remove an errant "M" on the certificate request signing page. Properly
wrap the text on that page for MacOS.
The TQSL version number is always displayed for command line usage
unless "-n" (check for new TQSL, configuration and program updates) is
used.
Added a new icon for TQSL contributed by K1GQ. The default shortcut
icon has not changed, but the new icon is available for selection.
Display an error when the TQSL configuration files (station locations,
callsign certificates, etc.) can't be opened. All earlier versions of
TQSL ignored these errors and started up with no callsign certificates
or station locations defined.
When a user selects a callsign in the Station Location window then
clicked on "Create new Station Location", the DXCC entity in the
station location wizard used the entity of the first callsign, not the
selected callsign.
The station location editor no longer shows multiple entries with the
same DXCC entity in the entity selection pulldown list when there are
multiple callsign certificates for a given callsign.
|
|
|
|
|
|
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.
|
