Log message:
py-*: remove unused tool dependency

py-setuptools includes the py-wheel functionality nowadays

Log message:
*: clean-up after python38 removal

Log message:
py-vdirsyncer: update to 0.19.3.

Version 0.19.3
==============

- Added a no_delete option to the storage configuration. :gh:`1090`
- Fix crash when running ``vdirsyncer repair`` on a collection. :gh:`1019`
- Add an option to request vCard v4.0.  :gh:`1066`
- Require matching ``BEGIN`` and ``END`` lines in vobjects. :gh:`1103`
- A Docker environment for Vdirsyncer has been added `Vdirsyncer DOCKERIZED \ 
<https://github.com/Bleala/Vdirsyncer-DOCKERIZED>`_.
- Implement digest auth. :gh:`1137`

Version 0.19.2
==============

- Improve the performance of ``SingleFileStorage``. :gh:`818`
- Properly document some caveats of the Google Contacts storage.
- Fix crash when using auth certs. :gh:`1033`
- The ``filesystem`` storage can be specified with ``type =
  "filesystem/icalendar"`` or ``type = "filesystem/vcard"``. \ 
This has not
  functional impact, and is merely for forward compatibility with the Rust
  implementation of vdirsyncer.
- Python 3.10 and 3.11 are officially supported.
- Instructions for integrating with Google CalDav/CardDav have changed.
  Applications now need to be registered as "Desktop applications". \ 
Using "Web
  application" no longer works due to changes on Google's side. :gh:`1078`

Version 0.19.1
==============

- Fixed crash when operating on Google Contacts. :gh:`994`
- The ``HTTP_PROXY`` and ``HTTPS_PROXY`` are now respected. :gh:`1031`
- Instructions for integrating with Google CalDav/CardDav have changed.
  Applications now need to be registered as "Web Application". :gh:`975`
- Various documentation updates.

Version 0.19.0
==============

- Add "shell" password fetch strategy to pass command string to a shell.
- Add "description" and "order" as metadata.  These fetch \ 
the CalDAV:
  calendar-description, ``CardDAV:addressbook-description`` and
  ``apple-ns:calendar-order`` properties respectively.
- Add a new ``showconfig`` status. This prints *some* configuration values as
  JSON. This is intended to be used by external tools and helpers that interact
  with ``vdirsyncer``, and considered experimental.
- Update TLS-related tests that were failing due to weak MDs. :gh:`903`
- ``pytest-httpserver`` and ``trustme`` are now required for tests.
- ``pytest-localserver`` is no longer required for tests.
- Multithreaded support has been dropped. The ``"--max-workers`` has been \ 
removed.
- A new ``asyncio`` backend is now used. So far, this shows substantial speed
  improvements in ``discovery`` and ``metasync``, but little change in `sync`.
  This will likely continue improving over time. :gh:`906`
- The ``google`` storage types no longer require ``requests-oauthlib``, but
  require ``python-aiohttp-oauthlib`` instead.
- Vdirsyncer no longer includes experimental support for `EteSync
  <https://www.etesync.com/>`_. The existing integration had not been supported
  for a long time and no longer worked. Support for external storages may be
  added if anyone is interested in maintaining an EteSync plugin. EteSync
  users should consider using `etesync-dav`_.
- The ``plist`` for macOS has been dropped. It was broken and homebrew
  generates their own based on package metadata. macOS users are encouraged to
  use that as a reference.

.. _etesync-dav: https://github.com/etesync/etesync-dav

Changes to SSL configuration
----------------------------

Support for ``md5`` and ``sha1`` certificate fingerprints has been dropped. If
you're validating certificate fingerprints, use ``sha256`` instead.

When using a custom ``verify_fingerprint``, CA validation is always disabled.

If ``verify_fingerprint`` is unset, CA verification is always active. Disabling
both features is insecure and no longer supported.

The ``verify`` parameter no longer takes boolean values, it is now optional and
only takes a string to a custom CA for verification.

The ``verify`` and ``verify_fingerprint`` will likely be merged into a single
parameter in future.

Log message:
py-vdirsyncer: not for Python 3.9

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

Log message:
py-vdirsyncer: back to 0.18.0; 0.19.2 is broken

Log message:
py-vdirsyncer: updated to 0.19.2

Version 0.19.2
==============

- Improve the performance of ``SingleFileStorage``. :gh:`818`
- Properly document some caveats of the Google Contacts storage.
- Fix crash when using auth certs. :gh:`1033`
- The ``filesystem`` storage can be specified with ``type =
  "filesystem/icalendar"`` or ``type = "filesystem/vcard"``. \ 
This has not
  functional impact, and is merely for forward compatibility with the Rust
  implementation of vdirsyncer.
- Python 3.10 and 3.11 are officially supported.
- Instructions for integrating with Google CalDav/CardDav have changed.
  Applications now need to be registered as "Desktop applications". \ 
Using "Web
  application" no longer works due to changes on Google's side. :gh:`1078`

Version 0.19.1
==============

- Fixed crash when operating on Google Contacts. :gh:`994`
- The ``HTTP_PROXY`` and ``HTTPS_PROXY`` are now respected. :gh:`1031`
- Instructions for integrating with Google CalDav/CardDav have changed.
  Applications now need to be registered as "Web Application". :gh:`975`
- Various documentation updates.

Version 0.19.0
==============

- Add "shell" password fetch strategy to pass command string to a shell.
- Add "description" and "order" as metadata.  These fetch \ 
the CalDAV:
  calendar-description, ``CardDAV:addressbook-description`` and
  ``apple-ns:calendar-order`` properties respectively.
- Add a new ``showconfig`` status. This prints *some* configuration values as
  JSON. This is intended to be used by external tools and helpers that interact
  with ``vdirsyncer``, and considered experimental.
- Update TLS-related tests that were failing due to weak MDs. :gh:`903`
- ``pytest-httpserver`` and ``trustme`` are now required for tests.
- ``pytest-localserver`` is no longer required for tests.
- Multithreaded support has been dropped. The ``"--max-workers`` has been \ 
removed.
- A new ``asyncio`` backend is now used. So far, this shows substantial speed
  improvements in ``discovery`` and ``metasync``, but little change in `sync`.
  This will likely continue improving over time. :gh:`906`
- The ``google`` storage types no longer require ``requests-oauthlib``, but
  require ``python-aiohttp-oauthlib`` instead.
- Vdirsyncer no longer includes experimental support for `EteSync
  <https://www.etesync.com/>`_. The existing integration had not been supported
  for a long time and no longer worked. Support for external storages may be
  added if anyone is interested in maintaining an EteSync plugin. EteSync
  users should consider using `etesync-dav`_.
- The ``plist`` for macOS has been dropped. It was broken and homebrew
  generates their own based on package metadata. macOS users are encouraged to
  use that as a reference.

Log message:
Mass-change BUILD_DEPENDS to TOOL_DEPENDS outside mk/.

Almost all uses, if not all of them, are wrong, according to the
semantics of BUILD_DEPENDS (packages built for target available for
use _by_ tools at build-time) and TOOL_DEPEPNDS (packages built for
host available for use _as_ tools at build-time).

No change to BUILD_DEPENDS as used correctly inside buildlink3.

As proposed on tech-pkg:
https://mail-index.netbsd.org/tech-pkg/2023/06/03/msg027632.html

Log message:
py-vdirsyncer: revert upgrade to 0.19

because of
https://github.com/pimutils/vdirsyncer/issues/1015

Log message:
py-vdirsyncer: update to 0.19.0.

Version 0.19.0
==============

- Add "shell" password fetch strategy to pass command string to a shell.
- Add "description" and "order" as metadata.  These fetch \ 
the CalDAV:
  calendar-description, ``CardDAV:addressbook-description`` and
  ``apple-ns:calendar-order`` properties respectively.
- Add a new ``showconfig`` status. This prints *some* configuration values as
  JSON. This is intended to be used by external tools and helpers that interact
  with ``vdirsyncer``, and considered experimental.
- Update TLS-related tests that were failing due to weak MDs. :gh:`903`
- ``pytest-httpserver`` and ``trustme`` are now required for tests.
- ``pytest-localserver`` is no longer required for tests.
- Multithreaded support has been dropped. The ``"--max-workers`` has been \ 
removed.
- A new ``asyncio`` backend is now used. So far, this shows substantial speed
  improvements in ``discovery`` and ``metasync``, but little change in `sync`.
  This will likely continue improving over time. :gh:`906`
- The ``google`` storage types no longer require ``requests-oauthlib``, but
  require ``python-aiohttp-oauthlib`` instead.
- Vdirsyncer no longer includes experimental support for `EteSync
  <https://www.etesync.com/>`_. The existing integration had not been supported
  for a long time and no longer worked. Support for external storages may be
  added if anyone is interested in maintaining an EteSync plugin. EteSync
  users should consider using `etesync-dav`_.
- The ``plist`` for macOS has been dropped. It was broken and homebrew
  generates their own based on package metadata. macOS users are encouraged to
  use that as a reference.

.. _etesync-dav: https://github.com/etesync/etesync-dav

Changes to SSL configuration
----------------------------

Support for ``md5`` and ``sha1`` certificate fingerprints has been dropped. If
you're validating certificate fingerprints, use ``sha256`` instead.

When using a custom ``verify_fingerprint``, CA validation is always disabled.

If ``verify_fingerprint`` is unset, CA verification is always active. Disabling
both features is insecure and no longer supported.

The ``verify`` parameter no longer takes boolean values, it is now optional and
only takes a string to a custom CA for verification.

The ``verify`` and ``verify_fingerprint`` will likely be merged into a single
parameter in future.