CVS commit: pkgsrc/databases/py-barman

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

Module Name:    pkgsrc
Committed By:   adam
Date:           Fri Oct  3 09:18:07 UTC 2025

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

Log Message:
py-barman: updated to 3.15.0

3.15.0

Notable changes

Allow incremental backups to be taken with compression and encryption
Previously, Barman prevented incremental backups to be taken if compression was enabled or if the parent backup was already compressed. Since encryption in Barman requires compression, this also 
meant that incremental backups could not be taken with encryption.

This limitation existed due to the complexity of restoring such backups, which involves multiple staging phases for decryption, decompression, and combination of backups.

After a significant refactoring effort, Barman now fully supports taking incremental backups with both compression and/or encryption. This allows for more flexible backup strategies, enabling users 
to take advantage of all available features without restrictions.

References: BAR-764, BAR-801, BAR-841.

Deprecate local_staging_path and recovery_staging_path configuration options
The local_staging_path and recovery_staging_path configuration options have been deprecated in favor of the new staging_path and staging_location options. The old options will continue to work for 
backwards compatibility, but users are encouraged to migrate to the new configuration options for better clarity and flexibility.

References: BAR-571, BAR-801.

Improve flexibility and consistency of staging area configuration
Whenever restoring a compressed, encrypted or incremental backup, Barman needs a staging area to handle intermediate files, such as decompressed or decrypted files, or the combined incremental backup 
data.

Previously, Barman used to have different configuration options for each scenario:

For incremental backups, the staging area was specified via the local_staging_path in the Barman configuration, which could only be a path in the Barman host.
For compressed backups, the staging area was specified via the recovery_staging_path, which could be a path in the Barman host (in case of local recovery) or a path in the target server (in case of 
remote recovery to a different server).
For encrypted backups, the staging area was specified via the local_staging_path in the Barman configuration, which could only be a path in the Barman host. Note that, since encryption requires 
compression to be enabled, when restoring an encrypted backup, users needed to specify both recovery_staging_path and local_staging_path.
Barman now provides a single, unified and more flexible staging area configuration:

The new staging_path configuration option can be used to specify an absolute path for the staging area, where intermediate files will be stored. The default value is /tmp.
The new staging_location configuration option can be used to specify whether the staging area is on the Barman host (local) or on the remote server (remote). The default value is local.
This means that, besides having a unified configuration for the staging path, users are now also able to specify with more flexibility where the staging area should be located, either on the Barman 
host or on the remote Postgres server.

Storage usage has also been optimized to reduce resource consumption whenever possible. This includes:

Removing intermediate files as soon as they are no longer needed.
Avoid using the staging area when not necessary, e.g. when restoring a compressed backup locally, no staging is needed and the backup is decompressed directly to its final destination.
This change simplifies configuration and improves consistency and resource usage, making the recovery management more transparent and predictable for end users.

References: BAR-764, BAR-765, BAR-801, BAR-841.


To generate a diff of this commit:
cvs rdiff -u -r1.28 -r1.29 pkgsrc/databases/py-barman/Makefile
cvs rdiff -u -r1.22 -r1.23 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.28 pkgsrc/databases/py-barman/Makefile:1.29
--- pkgsrc/databases/py-barman/Makefile:1.28    Wed May 28 04:57:01 2025
+++ pkgsrc/databases/py-barman/Makefile Fri Oct  3 09:18:07 2025
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.28 2025/05/28 04:57:01 adam Exp $
+# $NetBSD: Makefile,v 1.29 2025/10/03 09:18:07 adam Exp $
 
-DISTNAME=      barman-3.14.0
+DISTNAME=      barman-3.15.0
 PKGNAME=       ${PYPKGPREFIX}-${DISTNAME}
 CATEGORIES=    databases python
 MASTER_SITES=  ${MASTER_SITE_PYPI:=b/barman/}

Index: pkgsrc/databases/py-barman/distinfo
diff -u pkgsrc/databases/py-barman/distinfo:1.22 pkgsrc/databases/py-barman/distinfo:1.23
--- pkgsrc/databases/py-barman/distinfo:1.22    Wed May 28 04:57:01 2025
+++ pkgsrc/databases/py-barman/distinfo Fri Oct  3 09:18:07 2025
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.22 2025/05/28 04:57:01 adam Exp $
+$NetBSD: distinfo,v 1.23 2025/10/03 09:18:07 adam Exp $
 
-BLAKE2s (barman-3.14.0.tar.gz) = b4da940239fbf5ef406f34fd92f2847152e4d8e9f559043f05776e24ae2facc2
-SHA512 (barman-3.14.0.tar.gz) = 7f106e6cff33ae2208c7f262e728e268877d52a7149d6b98e5af543b177fdd0f48ae3b683b777d66ad38a4fdbb72ea33a84517cbf448fecd4d23502a12be77e5
-Size (barman-3.14.0.tar.gz) = 437078 bytes
+BLAKE2s (barman-3.15.0.tar.gz) = 08f988743aa8388d9b5d1bddaa9d91507bc6e7e952e563ade32ee5d4c9ed6283
+SHA512 (barman-3.15.0.tar.gz) = 4bbb86b6dcadfacaacf9e4dbb1cea3e33b155cb73be7752d58602fb2aa0b4145f7bf7aa96d3d687158e4035ece9aef5f47f2170c71ac405946573993b94262ca
+Size (barman-3.15.0.tar.gz) = 458105 bytes
 SHA1 (patch-barman_utils.py) = 0f93835a814bdd41c999dcebb34719312a74bd94