CVS commit: pkgsrc/databases/py-barman

["Adam Ciarcinski" <adam%netbsd.org@localhost>]

Module Name:    pkgsrc
Committed By:   adam
Date:           Mon Apr 14 11:09:15 UTC 2025

Modified Files:
        pkgsrc/databases/py-barman: Makefile PLIST distinfo

Log Message:
py-barman: updated to 3.13.2

3.13.2 (2025-03-27)

Minor changes

- Fix errors when using an immutable storage

  Added a new `worm_mode` configuration to enable WORM (Write Once Read Many)
  handling in Barman, allowing it to support backups on immutable storage.

  This fix also provides automatic relocation of the backup.info file in a new
  directory `meta` inside `backup_directory`. This will let Barman update it
  in future when needed.

  Barman will also _not_ purge the wals directory for WAL files that are not
  needed when running the first backup. This will add some extra space
  which will be reclaimed when this first backup is obsolete and removed
  (by that time, the backups and the WALs will be outside the retention
  policy window).

  Added additional notes to the documentation explaining limitations when
  running with an immutable storage for backups. In particular the need
  for a grace period in the immutability of files and the fact that
  `barman keep` is not supported in these environments.

  References: BAR-649, BAR-645, BAR-650, BAR-651, BAR-652.

3.13.1 (2025-03-20)

Minor changes

- Improve behavior of the backup shortcuts `last-full` / `latest-full`

  The shortcuts `last-full` / `latest-full` were retrieving not the last full backup of
  the server, but the last full backup of the server which was eligible as the parent
  for an incremental backup.

  While this was the expected behavior, the feedback from the community has shown that
  it was confusing for the users.

  From now on, the shortcuts `last-full` / `latest-full` will retrieve the last full
  backup of the Barman server, independently if that backup is eligible as the parent
  for an incremental backup or not.

  The eligibility of the full backup as the parent of an incremental backup will still
  be validated by Barman in a later step, and a proper message will be displayed in
  case it doesn't suit as a parent.


To generate a diff of this commit:
cvs rdiff -u -r1.25 -r1.26 pkgsrc/databases/py-barman/Makefile
cvs rdiff -u -r1.8 -r1.9 pkgsrc/databases/py-barman/PLIST
cvs rdiff -u -r1.19 -r1.20 pkgsrc/databases/py-barman/distinfo

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Modified files:

Index: pkgsrc/databases/py-barman/Makefile
diff -u pkgsrc/databases/py-barman/Makefile:1.25 pkgsrc/databases/py-barman/Makefile:1.26
--- pkgsrc/databases/py-barman/Makefile:1.25    Fri Mar 14 12:36:01 2025
+++ pkgsrc/databases/py-barman/Makefile Mon Apr 14 11:09:15 2025
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.25 2025/03/14 12:36:01 adam Exp $
+# $NetBSD: Makefile,v 1.26 2025/04/14 11:09:15 adam Exp $
 
-DISTNAME=      barman-3.13.0
+DISTNAME=      barman-3.13.2
 PKGNAME=       ${PYPKGPREFIX}-${DISTNAME}
 CATEGORIES=    databases python
 MASTER_SITES=  ${MASTER_SITE_PYPI:=b/barman/}
@@ -10,7 +10,7 @@ HOMEPAGE=     https://pgbarman.org/
 COMMENT=       Backup and Recovery Manager for PostgreSQL
 LICENSE=       gnu-gpl-v3
 
-TOOL_DEPENDS+= ${PYPKGPREFIX}-setuptools-[0-9]*:../../devel/py-setuptools
+TOOL_DEPENDS+= ${PYPKGPREFIX}-setuptools>=78:../../devel/py-setuptools
 DEPENDS+=      ${PYPKGPREFIX}-argcomplete-[0-9]*:../../devel/py-argcomplete
 DEPENDS+=      ${PYPKGPREFIX}-dateutil-[0-9]*:../../time/py-dateutil
 DEPENDS+=      ${PYPKGPREFIX}-psycopg2>=2.4.2:../../databases/py-psycopg2

Index: pkgsrc/databases/py-barman/PLIST
diff -u pkgsrc/databases/py-barman/PLIST:1.8 pkgsrc/databases/py-barman/PLIST:1.9
--- pkgsrc/databases/py-barman/PLIST:1.8        Mon Jan 27 09:31:46 2025
+++ pkgsrc/databases/py-barman/PLIST    Mon Apr 14 11:09:15 2025
@@ -1,4 +1,4 @@
-@comment $NetBSD: PLIST,v 1.8 2025/01/27 09:31:46 adam Exp $
+@comment $NetBSD: PLIST,v 1.9 2025/04/14 11:09:15 adam Exp $
 bin/barman
 bin/barman-cloud-backup
 bin/barman-cloud-backup-delete
@@ -11,12 +11,12 @@ bin/barman-cloud-wal-archive
 bin/barman-cloud-wal-restore
 bin/barman-wal-archive
 bin/barman-wal-restore
-${PYSITELIB}/${WHEEL_INFODIR}/AUTHORS
-${PYSITELIB}/${WHEEL_INFODIR}/LICENSE
 ${PYSITELIB}/${WHEEL_INFODIR}/METADATA
 ${PYSITELIB}/${WHEEL_INFODIR}/RECORD
 ${PYSITELIB}/${WHEEL_INFODIR}/WHEEL
 ${PYSITELIB}/${WHEEL_INFODIR}/entry_points.txt
+${PYSITELIB}/${WHEEL_INFODIR}/licenses/AUTHORS
+${PYSITELIB}/${WHEEL_INFODIR}/licenses/LICENSE
 ${PYSITELIB}/${WHEEL_INFODIR}/top_level.txt
 ${PYSITELIB}/barman/__init__.py
 ${PYSITELIB}/barman/__init__.pyc

Index: pkgsrc/databases/py-barman/distinfo
diff -u pkgsrc/databases/py-barman/distinfo:1.19 pkgsrc/databases/py-barman/distinfo:1.20
--- pkgsrc/databases/py-barman/distinfo:1.19    Fri Mar 14 12:36:01 2025
+++ pkgsrc/databases/py-barman/distinfo Mon Apr 14 11:09:15 2025
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.19 2025/03/14 12:36:01 adam Exp $
+$NetBSD: distinfo,v 1.20 2025/04/14 11:09:15 adam Exp $
 
-BLAKE2s (barman-3.13.0.tar.gz) = 546f4c39c69cde81dd4ee863d2d5ae4eeae5b19aada11064694c1eeeeb5ded13
-SHA512 (barman-3.13.0.tar.gz) = 9c31da9c1fb1ffb19f440e22056636f861af93a846185178784f935aae5df4358a94aa3ab97e486ead1ea1f37fb5b38ffac25287372c72e128e0094bb0bf5e30
-Size (barman-3.13.0.tar.gz) = 415862 bytes
+BLAKE2s (barman-3.13.2.tar.gz) = 44370fd38f815cb83edb571f7d9c1b09aac125414306687137705ff18830017f
+SHA512 (barman-3.13.2.tar.gz) = ff3589b535548654281f602a2fbf84979fbe9ad808d5b186b451f56118ca63dd8243d4e49b6c0687c2502aaf17cfb583295241fba7fe52849dc93598242feed4
+Size (barman-3.13.2.tar.gz) = 418767 bytes
 SHA1 (patch-barman_utils.py) = 0f93835a814bdd41c999dcebb34719312a74bd94