Log message:
py-borgbackup: updated to 1.4.0

borg 1.2.x to 1.4.x
-------------------

If you currently use borg 1.2.5+: no upgrade steps needed (if you already did
them when upgrading to that version, otherwise see below).

If you currently use borg 1.2.0 .. 1.2.4, read and follow "Pre-1.2.5 archives
spoofing vulnerability (CVE-2023-36811)" section, see the top of this changelog.

Compatibility notes:

By default, borg 1.4 will behave quite similar to borg 1.2 (it was forked off
from 1.2-maint branch at 1.2.7).

- the slashdot hack: be careful not to accidentally give paths containing /./
  to "borg create" if you do not want to trigger this feature (which \ 
strips the
  left part of the path from archived items).
- BORG_EXIT_CODES=modern is a feature that borg script, wrapper and GUI authors
  may want to use to get more specific error and warning return codes from borg.
  In that case, of course they will need to make sure to correctly deal with these
  new codes, see the internals/frontends docs.

Log message:
py-*: remove unused tool dependency

py-setuptools includes the py-wheel functionality nowadays

Log message:
sysutils/py-borgbackup: make this accept a newer py-msgpack.

This is in contravention to the upstream policy which insists that
because the maintainers of py-msgpack in the distant past made a
non-compatible change (apparently in a version before 0.5.6 of
py-msgpack, many, many years ago), they now insist that you *cannot*
use a newer version of py-msgpack than what the code insists on,
ref.

   https://github.com/borgbackup/borg/issues/3753

This collides (hard) with the pkgsrc default stance which is to
"upgrade everything to the newest available version", and makes
this package break each time a new version of py-msgpack is integrated
in pkgsrc.

For now just patch this to accept py-msgpack versions between
0.5.6 and 1.1.0 and not just between 0.5.6 and 1.0.8.

At least testing by doing a backup run makes that backup run
complete successfully with py-mgspack 1.1.0 installed, instead
of a sour error message that a non-supported version of msgpack
is installed.

Log message:
py-borgbackup: add comment how to run the self tests once 2.x is released

Log message:
py-borgbackup: updated to 1.2.8

Version 1.2.8 (2024-03-29)

For upgrade and compatibility hints, please also read the section "Upgrade \ 
Notes"
above.

Fixes:

- check: fix return code and log level for index entry value discrepancies
- with-lock: catch FileNotFoundError exception, print error msg
- benchmark: inherit options --rsh --remote-path
- fix Ctrl-C / SIGINT behaviour for pyinstaller-made binaries

New features:

- upgrade --check-tam: check manifest TAM auth,
  exit with rc=1 if there are issues.
- upgrade --check-archives-tam: check archives TAM auth,
  exit with rc=1 if there are issues.

Other changes:

- allow msgpack 1.0.8 (this might fix memory leaks with Python 3.12)
- use the latest Cython 0.29.x
- vagrant:

  - use / build binaries with python 3.9.19
  - use generic/openbsd7 box
- docs:

  - simplify TAM-related upgrade docs using the new commands
  - improve docs for borg with-lock
  - add more infos borg check --repair recreating the shadow index
    to change log

Log message:
py-borgbackup: updated to 1.2.7

Version 1.2.7 (2023-12-02)
--------------------------

For upgrade and compatibility hints, please also read the section "Upgrade \ 
Notes"
above.

Fixes:

- docs: CVE-2023-36811 upgrade steps: consider checkpoint archives,
- check/compact: fix spurious reappearance of orphan chunks since borg 1.2,
  this consists of 2 fixes:

  - for existing chunks: check --repair: recreate shadow index,
  - for newly created chunks: update shadow index when doing a double-put,
- LockRoster.modify: no KeyError if element was already gone,
- create --X-from-command: run subcommands with a clean environment,
- list --sort-by: support "archive" as alias of "name",
- fix rc and msg if arg parsing throws an exception,

Other changes:

- support and test on Python 3.12
- include unistd.h in _chunker.c (fix for Python 3.13)
- allow msgpack 1.0.6 and 1.0.7
- TAM issues: show tracebacks, improve borg check logging,
- replace "datetime.utcfromtimestamp" with custom helper to avoid
  deprecation warnings when using Python 3.12
- vagrant:

  - use generic/debian9 box, fixes
  - add VM with debian bookworm / test on OpenSSL 3.0.x.
- docs:

  - not only attack/unsafe, can also be a fs issue,
  - point to CVE-2023-36811 upgrade steps from borg 1.1 to 1.2 upgrade steps,
  - upgrade steps needed for all kinds of repos (including "none" \ 
encryption mode),
  - upgrade steps: talk about consequences of borg check,
  - upgrade steps: remove period that could be interpreted as part of the command
  - automated-local.rst: use GPT UUID for consistent udev rule
  - create disk/partition sector backup by disk serial number,
  - update macOS hint about full disk access
  - clarify borg prune -a option description,
  - readthedocs: also build offline docs (HTMLzip),
  - frontends: add "check.rebuild_refcounts" message

Log message:
*: bump for openssl 3

Log message:
py-borgbackup: accept newer py-msgpack versions

Bump PKGREVISION.