Log message:
*: recursive bump for pcre2
Running an old binary against the new pcre doesn't work:
/usr/pkg/lib/libpcre2-8.so.0: version PCRE2_10.47 required by \ 
/usr/pkg/lib/libglib-2.0.so.0 not defined

Log message:
*: rev bump for curl

Log message:
*: recursive bump for tiff growing lerc dependency

Log message:
(ham/trustedQSL) Updated 2.8 to 2.8.1
https://www.arrl.org/files/file/LoTW%20Instructions/TrustedQSL-2-8-1-release.pdf
Trusted QSL V2.8.1 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.8
This release includes an update to the most recent TQSL configuration file.
This release repairs two serious defects in TQSL 2.8. First, it
corrects an issue where some QSOs would not be signed when an ADIF
file contained a mismatched gridsquare. Second, the checking of the
content of MY_COUNTRY was removed as this is a human-readable string
and not expected to conform to a strict enumeration.
TQSL 2.8.1 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 "/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.1 will replace older versions of Trusted QSL while
preserving your Callsign Certificates, Station Locations, and
preferences.  On Windows, simply run the TQSL 2.8.1 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.1
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:
[2.8.1]
Correct handing of ADIF files with gridsquares provided for the
operator's station for cases where the Station Location grid was not
the same length as the ADIF MY_GRIDSQUARE tag. This defect caused
those QSOs to be ignored and not signed.
Remove checking of MY_COUNTRY as its not intended to be a rigidly
defined field. Users had values which were abbreviated, using emtity
codes, etc. TQSL only uses that field if it matches an Entity name
precisely. MY_DXCC is preferred for specifying entity numbers.  Major
feature Additions: None.
Minor Updates:
Correct the Russssian translation files.
Correct a small number of VUCC grid entries in the vuccgrids.dat file,
as well as adding a version number header to that file.
Fix a compiler warning reported for some Linux distributions.
Reinstalling TQSL 2.7.x
Downgrading to TQSL 2.8 can be seamlessly performed by uninstalling
TQSL 2.8.1 and reinstalling TQSL 2.8. (TQSL 2.7.5 is recommended for a
downgrade due to the defects in TQSL 2.8).

Log message:
(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.

Log message:
*: recursive bump for jpeg -> libjpeg-turbo switch

Log message:
*: recursive bump for default Kerberos implementation switch

Log message:
*: recursive bump for icu 77 and libxml2 2.14