Log message:
*: clean-up after python38 removal

Log message:
filesystems/tahoe-lafs: Update HOMEPAGE (https, follow redirect)

Log message:
filesystems/tahoe-lafs: Update to 1.19.0

Note that tahoe fails because it has not adapted to API withdrawals in
py-attrs.  However 1.18.0 fails the same way, so having 1.19.0 almost
working seems better.  Reverting py-attrs to 2024Q2 should make tahoe
work.

Release 1.19.0 (2024-01-04)
===========================

Features
--------

- Tahoe-LAFS now includes a new "Grid Manager" specification and
  implementation adding more options to control which storage servers
  a client will use for uploads. (`#2916
  <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2916>`_)

- Added support for Python 3.12, and work with Eliot 1.15 (`#3072
  <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3072>`_)

- `tahoe run ...` will now exit when its stdin is closed.

  This facilitates subprocess management, specifically cleanup.  When
  a parent process is running tahoe and exits without time to do
  "proper" cleanup at least the stdin descriptor will be closed.
  Subsequently "tahoe run" notices this and exits. (`#3921
  <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3921>`_)

- Mutable objects can now be created with a pre-determined "signature
  key" using the ``tahoe put`` CLI or the HTTP API.  This enables
  deterministic creation of mutable capabilities.  This feature must
  be used with care to preserve the normal security and reliability
  properties. (`#3962
  <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3962>`_)

- Added support for Python 3.11. (`#3982
  <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3982>`_)

- tahoe run now accepts --allow-stdin-close to mean "keep running if stdin \ 
closes" (`#4036 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4036>`_)

- The storage server and client now support a new, HTTPS-based protocol. (`#4041 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4041>`_)

- Some operations now run in threads, improving the responsiveness of
  Tahoe nodes. (`#4068
  <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4068>`_)

- Logs are now written in a thread, which should make the application
  more responsive under load. (`#4804
  <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4804>`_)

Log message:
*: latest py-sphinx only support Python 3.9+

Log message:
*: recursive bump for Python 3.11 as new default

Log message:
py-ZopeInterface: moved to py-zope.interface

Log message:
Convert several packages to using versioned_depends for py-cryptography.

Somehow this has been hanging around in my tree for months.

Log message:
filesystems/tahoe-lafs: Update to 1.18.0

packaging changes: Drop explanation about python 2.7 being supported
by upstream and $MAINTAINER not wanting to deal with dependencies.

Upstream NEWS:

Release 1.18.0 (2022-10-02)
'''''''''''''''''''''''''''

Backwards Incompatible Changes
------------------------------

- Python 3.6 is no longer supported, as it has reached end-of-life and is no \ 
longer receiving security updates. (`#3865 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3865>`_)
- Python 3.7 or later is now required; Python 2 is no longer supported. (`#3873 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3873>`_)
- Share corruption reports stored on disk are now always encoded in UTF-8. \ 
(`#3879 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3879>`_)
- Record both the PID and the process creation-time:

  a new kind of pidfile in `running.process` records both
  the PID and the creation-time of the process. This facilitates
  automatic discovery of a "stale" pidfile that points to a
  currently-running process. If the recorded creation-time matches
  the creation-time of the running process, then it is a still-running
  `tahoe run` process. Otherwise, the file is stale.

  The `twistd.pid` file is no longer present. (`#3926 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3926>`_)

Features
--------

- The implementation of SDMF and MDMF (mutables) now requires RSA keys to be \ 
exactly 2048 bits, aligning them with the specification.

  Some code existed to allow tests to shorten this and it's
  conceptually possible a modified client produced mutables
  with different key-sizes. However, the spec says that they
  must be 2048 bits. If you happen to have a capability with
  a key-size different from 2048 you may use 1.17.1 or earlier
  to read the content. (`#3828 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3828>`_)
- "make" based release automation (`#3846 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3846>`_)

Log message:
*: Revbump packages that use Python at runtime without a PKGNAME prefix

Log message:
filesystems/tahoe-lafs: Update to 1.17.1

Upstream NEWS, omitting bugfixes and minor improvements:

Release 1.17.0 (2021-12-06)
'''''''''''''''''''''''''''

Security-related Changes
------------------------

- The introducer server no longer writes the sensitive introducer fURL value to \ 
its log at startup time.  Instead it writes the well-known path of the file from \ 
which this value can be read. (`#3819 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3819>`_)
- The storage protocol operation ``readv`` now safely rejects attempts to read \ 
negative lengths.
  Previously these read requests were satisfied with the complete contents of \ 
the share file (including trailing metadata) starting from the specified offset. \ 
(`#3822 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3822>`_)
- The storage server implementation no longer records corruption advisories \ 
about storage indexes for which it holds no shares. (`#3824 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3824>`_)
- The lease-checker now uses JSON instead of pickle to serialize its state.

  tahoe will now refuse to run until you either delete all pickle files or
  migrate them using the new command::

      tahoe admin migrate-crawler

  This will migrate all crawler-related pickle files. (`#3825 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3825>`_)
- The SFTP server no longer accepts password-based credentials for authentication.
  Public/private key-based credentials are now the only supported authentication \ 
type.
  This removes plaintext password storage from the SFTP credentials file.
  It also removes a possible timing side-channel vulnerability which might have \ 
allowed attackers to discover an account's plaintext password. (`#3827 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3827>`_)
- The storage server now keeps hashes of lease renew and cancel secrets for \ 
immutable share files instead of keeping the original secrets. (`#3839 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3839>`_)
- The storage server now keeps hashes of lease renew and cancel secrets for \ 
mutable share files instead of keeping the original secrets. (`#3841 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3841>`_)

Features
--------

- Tahoe-LAFS releases now have just a .tar.gz source release and a (universal) \ 
wheel (`#3735 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3735>`_)
- tahoe-lafs now provides its statistics also in OpenMetrics format (for \ 
Prometheus et. al.) at `/statistics?t=openmetrics`. (`#3786 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3786>`_)
- If uploading an immutable hasn't had a write for 30 minutes, the storage \ 
server will abort the upload. (`#3807 \ 
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3807>`_)

Removed Features
----------------

- The little-used "control port" has been removed from all node types. \ 
(`#3814 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3814>`_)