Log message:
*: bump for openssl 3

Log message:
tarsnap: update to 1.0.40.

Tarsnap 1.0.40 is now available.  This version brings several improvements
compared to tarsnap 1.0.39:

* tarsnap now accepts a --resume-extract option to skip extracting files whose
  filesize and mtime match existing files on disk.

* tarsnap now accepts --progress-bytes SIZE, which prints a progress message
  after each SIZE bytes are processed, up to once per file.  This can be
  disabled with --no-progress-bytes.

* tarsnap now accepts a --passphrase method:arg option which accepts:
  * --passphrase dev:tty-stdin
  * --passphrase dev:stdin-once
  * --passphrase dev:tty-once
  * --passphrase env:VARNAME
  * --passphrase file:FILENAME

* tarsnap now accepts a --dump-config option to print the command-line and all
    non-blank lines read from config files.

* tarsnap now exits with an error if there are unused command-line arguments.
  (i.e. "tarsnap -d -f a1 a2", where "a2" is unused.)

* Improved performance on some x86, amd64, and arm64 systems by using
  cryptographic instruction set extensions.

* When sent SIGINFO or SIGUSR1, tarsnap now prints the number of files and the
  number of uncompressed bytes processed, in addition to the previous output.

* A zsh completion file can be installed with
  configure --with-zsh-completion=DIR.

As usual, there are also lots of minor build fixes, harmless bug fixes, and
code cleanups.

Log message:
sysutils: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Log message:
sysutils: Remove SHA1 hashes for distfiles

Log message:
Support PKG_SYSCONFDIR. Bump PKGREVISION.

Log message:
*: Recursive revision bump for openssl 1.1.1.

Log message:
Updated tarsnap to 1.0.39.

Tarsnap 1.0.39 is now available.  (Yes, just 2 weeks after 1.0.38.)  This
version brings several important bug fixes:

* tarsnap 1.0.38 (but not earlier versions) would exit with an assertion
failure after successfully creating an archive containing a file with a
"last modified" time prior to January 1st, 1970.

* tarsnap 1.0.38 and earlier could crash if instructed to archive the
contents of corrupt cpio or ar archives (via the @archive directive).

* tarsnap 1.0.38 and earlier could crash if passed an invalidly encrypted
key file.

Log message:
Updated tarsnap to 1.0.38.

Tarsnap 1.0.38 is now available.  This version brings several new features
compared to tarsnap 1.0.37:

* Tarsnap now supports OpenSSL 1.1.

* tarsnap accepts an --iso-dates option, which causes times to be printed in
YYYY-MM-DD HH:MM:SS format rather than the traditional unix "ls -l" style.

* tarsnap accepts a --force-resources option to proceed with decryption of a
passphrase-encrypted key file even if it is anticipated to use an excessive
amount of memory or CPU time.  (This may be useful if tarsnap inaccurately
estimates the amount of memory your system has available.)

* tarsnap accepts an --archive-names <file> option, which reads a list of
archive names to operate on when operating in -d and --print-stats modes.
(This should make some scripts simpler; no more need to construct a command
line which has '-f' inserted before each archive name.)

Potentially (but unlikely) breaking changes in this code compared to tarsnap
1.0.37:

* tarsnap now applies the --humanize-numbers option to the "progress" \ 
output
printed by SIGINFO / SIGUSR1.  If you have scripts which send signals to
tarsnap and parse its output, they may need to be updated.

* tarsnap -v now prints 'Deleting archive "foo"' even if only one \ 
archive is
being deleted.  If you have scripts which parse the output of tarsnap -v,
they may need to be updated.

* tarsnap now prints a warning if you pass '--configfile /nosuchfile'.  If you
have scripts which rely on being able to specify nonexistent configuration
files and not get any warnings from tarsnap, they may need to be updated.
(Also, if you were doing that, I *really* want to know why.)

There are also two changes which most users should not encounter:

* tarsnap now has an --initialize-cachedir mode; this is intended for use by
the GUI.  (The cache directory will be initialized automatically in normal
usage of the tarsnap command-line utility.)

* tarsnap's configure script takes a --with-conf-no-sample option which
results in the sample tarsnap configuration file being installed as
"tarsnap.conf" rather than "tarsnap.conf.sample".  This is \ 
intended for use in
some packaging systems which have mechanisms for managing configuration files,
and should probably not be used by hand (since it will overwrite your existing
tarsnap.conf).