borgbackup 1.4.2__tar.gz → 1.4.4__tar.gz

{borgbackup-1.4.2 → borgbackup-1.4.4}/CHANGES.rst

@@ -414,7 +414,7 @@ Compatibility notes:
 Change Log
 ==========
 
-Version 1.4.2 (2025-10-31)
+Version 1.4.4 (2026-03-19)
 --------------------------
 
 For upgrade and compatibility hints, please also read the "Upgrade Notes" section
@@ -422,6 +422,85 @@ above.
 
 New features:
 
+- prune: added -v / --info output, #9262.
+- mount: warn about symlinks pointing outside of the mount point, #9254.
+- create/info: remember/show cwd at the time of archive creation, #6191.
+
+Fixes:
+
+- hashindex: fix memory leak, #9497.
+- hashindex: check values in read HashHeader, #9485.
+- hashindex_size: return int64_t, #9423.
+- hashindex: fix iteritems segfaulting with non-existent marker, #9368.
+  Never happened in borg, because borg always gives existing markers to iteritems.
+- compress: make Padme size obfuscation usable ("obfuscate,250,...").
+- borgfs/mount: get_base_dir: avoid using incorrect HOME, #3395.
+
+Other changes:
+
+- PyInstaller binary: do not exclude SSL, needed for pyfuse3/trio, #9196.
+- mount: FUSE FS performance improvement.
+- warn when replaying segments, #9233.
+- CI / tests:
+
+  - build Linux binaries with pyfuse3.
+  - use macOS 15 to build the binaries.
+  - scripts/linux-run: run commands (e.g. tox) in a Podman Linux container.
+  - fix race condition in test_with_lock, #8810.
+  - fix spurious sparse test failure on Win32, #7616.
+  - Cygwin: skip ~root base dir test.
+  - fix coverage collection for daemonized `borg mount`, #9448.
+- docs:
+
+  - move RTD version selector to sidebar top-left, #8204.
+  - consolidate key backup info in `borg key export` help, #6204.
+  - clarify append-only != write-only, #9304.
+  - fix typos found by codespell.
+  - update binary README.
+  - GitHub: enhance pull request template.
+
+
+Version 1.4.3 (2025-12-02)
+--------------------------
+
+New features:
+
+- None.
+
+Fixes:
+
+- compact: replace AssertionError with a warning, #8535.
+- compact: also fix segment hints data for lost segment files.
+- CI: FUSE-related fixes and improvements, #9182:
+
+  - The Linux and FreeBSD binaries built on GitHub now include working
+    FUSE support (based on llfuse).
+  - We can't include FUSE support in the macOS binaries built on GitHub,
+    because we can't install macFUSE there; use our Homebrew tap for that.
+
+Other changes:
+
+- Drop Python 3.9 support (has reached end of life at python.org).
+- CI:
+
+  - Install the correct FUSE library depending on the tox environment.
+  - PyInstaller binary building: build and upload early, then run CI tests.
+  - For now, use llfuse, as there is an issue with PyInstaller and pyfuse3.
+  - Backported vm_tests (FreeBSD/NetBSD/OpenBSD/Haiku) from the master branch.
+  - Dynamic code analysis (Address and Undefined Behavior Sanitizers), #6819.
+  - Add tag-based workflows and provenance attestation for GitHub-built
+    binaries, #9135, #9136.
+- Docs:
+
+  - Some fixes and updates to the FAQ, #9188.
+  - Update binary README; release binaries are built on GitHub now.
+
+
+Version 1.4.2 (2025-10-31)
+--------------------------
+
+New features:
+
 - BORG_MSGPACK_VERSION_CHECK=no to optionally disable the msgpack version
   check; default is "yes"; use at your own risk, #9109.
 - fat binary builds on GitHub (see assets on the GitHub releases page):

{borgbackup-1.4.2 → borgbackup-1.4.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: borgbackup
-Version: 1.4.2
+Version: 1.4.4
 Summary: Deduplicated, encrypted, authenticated and compressed backups
 Author: The Borg Collective (see AUTHORS file)
 Maintainer-email: Thomas Waldmann <tw@waldmann-edv.de>
@@ -21,7 +21,6 @@ Classifier: Operating System :: MacOS :: MacOS X
 Classifier: Operating System :: POSIX :: Linux
 Classifier: Programming Language :: Python
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.9
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
@@ -29,7 +28,7 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Security :: Cryptography
 Classifier: Topic :: System :: Archiving :: Backup
-Requires-Python: >=3.9
+Requires-Python: >=3.10
 License-File: LICENSE
 License-File: AUTHORS
 Requires-Dist: msgpack<=1.1.2,>=1.0.3

{borgbackup-1.4.2 → borgbackup-1.4.4}/docs/_templates/layout.html

@@ -17,6 +17,7 @@
   {% if theme_touch_icon %}
   <link rel="apple-touch-icon" href="{{ pathto('_static/' ~ theme_touch_icon, 1) }}" />
   {% endif %}
+  <meta name="readthedocs-addons-api-version" content="1" />
   {{ super() }}
 {% endblock %}
 

borgbackup-1.4.4/docs/_templates/versionselector.html

@@ -0,0 +1,29 @@
+<div class="version-selector" id="borg-version-selector" style="display:none;">
+  <label for="version-select">Select your Borg version:</label>
+  <select id="version-select"></select>
+</div>
+<script type="text/javascript">
+  // Populate the version selector using ReadTheDocs data if available.
+  function borgInitVersionSelector(data) {
+    var versions = data && data.versions && data.versions.active;
+    if (!versions || !versions.length) return;
+    var current = data.versions && data.versions.current && data.versions.current.slug;
+    var select = document.getElementById("version-select");
+    if (!select) return;
+    versions.forEach(function(v) {
+      var opt = document.createElement("option");
+      opt.value = v.urls.documentation;
+      opt.textContent = v.slug;
+      if (v.slug === current) opt.selected = true;
+      select.appendChild(opt);
+    });
+    select.addEventListener("change", function() {
+      window.location.href = this.value;
+    });
+    document.getElementById("borg-version-selector").style.display = "";
+  }
+
+  document.addEventListener("readthedocs-addons-data-ready", function(event) {
+    borgInitVersionSelector(event.detail.data());
+  });
+</script>

{borgbackup-1.4.2 → borgbackup-1.4.4}/docs/binaries/00_README.txt

@@ -34,32 +34,29 @@ Binaries built on GitHub servers
 borg-linux-glibc235-x86_64-gh Linux AMD/Intel (built on Ubuntu 22.04 LTS with glibc 2.35)
 borg-linux-glibc235-arm64-gh  Linux ARM (built on Ubuntu 22.04 LTS with glibc 2.35)
 
-borg-macos-14-arm64-gh        macOS Apple Silicon (built on macOS 14 w/o FUSE support)
-borg-macos-13-x86_64-gh       macOS Intel (built on macOS 13 w/o FUSE support)
+borg-macos-15-arm64-gh        macOS Apple Silicon (built on macOS 15 w/o FUSE support)
+borg-macos-15-x86_64-gh       macOS Intel (built on macOS 15 w/o FUSE support)
 
+borg-freebsd-14-x86_64-gh     FreeBSD AMD/Intel (built on FreeBSD 14)
 
 Binaries built locally
 ~~~~~~~~~~~~~~~~~~~~~~
 
-borg-linux-glibc241-x86_64 Linux (built on Debian 13 "Trixie" with glibc 2.41)
-borg-linux-glibc236-x86_64 Linux (built on Debian 12 "Bookworm" with glibc 2.36)
 borg-linux-glibc231-x86_64 Linux (built on Debian 11 "Bullseye" with glibc 2.31)
 
-borg-freebsd-13-x86_64     FreeBSD (built on FreeBSD 13)
-borg-freebsd-14-x86_64     FreeBSD (built on FreeBSD 14)
+Note: if you don't find a specific binary here, check release 1.4.1 or 1.2.9.
 
 
 Verifying your download
 -----------------------
 
-Please check the GPG signature to make sure you received the binary as I have
-built it.
+I provide GPG signatures for files which I have built locally on my machines.
 
-To check the GPG signature, download both the binary and the corresponding
-*.asc file and then (on the shell) type, for example:
+To check the GPG signature, download both the file and the corresponding
+signature (*.asc file) and then (on the shell) type, for example:
 
     gpg --recv-keys 9F88FB52FAF7B393
-    gpg --verify borg-freebsd.asc borg-freebsd
+    gpg --verify borgbackup.tar.gz.asc borgbackup.tar.gz
 
 The files are signed by:
 
@@ -69,6 +66,24 @@ GPG key fingerprint: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393
 My fingerprint is also in the footer of all my BorgBackup mailing list posts.
 
 
+Provenance attestations for GitHub-built binaries
+-------------------------------------------------
+
+For binaries built on GitHub (files with a "-gh" suffix in the name), we publish
+an artifact provenance attestation that proves the binary was built by our
+GitHub Actions workflow from a specific commit or tag. You can verify this using
+the GitHub CLI (gh). Install it from https://cli.github.com/ and make sure you
+use a recent version that supports "gh attestation".
+
+Practical example (Linux, 1.4.3 tag):
+
+    curl -LO https://github.com/borgbackup/borg/releases/download/1.4.3/borg-linux-glibc235-x86_64-gh
+    gh attestation verify --repo borgbackup/borg --source-ref refs/tags/1.4.3 borg-linux-glibc235-x86_64-gh
+
+If verification succeeds, gh prints a summary stating the subject (your file),
+that it was attested by GitHub Actions, and the job/workflow reference.
+
+
 Installing
 ----------
 

{borgbackup-1.4.2 → borgbackup-1.4.4}/docs/borg_theme/css/borg.css

@@ -194,3 +194,45 @@ cite {
 #common-options .option {
     white-space: nowrap;
 }
+/* Remove the right-column max-width cap so content fills the full available width. */
+#right-column {
+    max-width: none;
+}
+/* Hide the default RTD flyout since we show the version selector in the sidebar. */
+readthedocs-flyout {
+    display: none !important;
+}
+/* Version selector in the sidebar. */
+.version-selector {
+    padding: 0 22px;
+    margin: 7px 0 7px 0;
+    font-size: 14px;
+}
+.version-selector label {
+    display: block;
+    margin-bottom: 4px;
+    color: #000;
+}
+.version-selector select {
+    width: 100%;
+    padding: 4px;
+    background-color: #fafafa;
+    color: #000;
+    border: 1px solid #ccc;
+    border-radius: 3px;
+}
+.version-selector::after {
+    content: '';
+    display: block;
+    border-top: 1px solid #ccc;
+    margin: 7px 0 0 0;
+}
+/* Reduce top and bottom margin of searchbox block to 7px to match separator spacing. */
+.sidebar-block:has(#main-search) {
+    margin-top: 7px;
+    margin-bottom: 7px;
+}
+/* Reduce the separator margin below the search block to 7px. */
+.sphinxsidebar > .sidebar-block:has(#main-search):after {
+    margin: 7px 22px 0 22px;
+}

{borgbackup-1.4.2 → borgbackup-1.4.4}/docs/changes.rst

@@ -414,7 +414,7 @@ Compatibility notes:
 Change Log
 ==========
 
-Version 1.4.2 (2025-10-31)
+Version 1.4.4 (2026-03-19)
 --------------------------
 
 For upgrade and compatibility hints, please also read the "Upgrade Notes" section
@@ -422,6 +422,85 @@ above.
 
 New features:
 
+- prune: added -v / --info output, #9262.
+- mount: warn about symlinks pointing outside of the mount point, #9254.
+- create/info: remember/show cwd at the time of archive creation, #6191.
+
+Fixes:
+
+- hashindex: fix memory leak, #9497.
+- hashindex: check values in read HashHeader, #9485.
+- hashindex_size: return int64_t, #9423.
+- hashindex: fix iteritems segfaulting with non-existent marker, #9368.
+  Never happened in borg, because borg always gives existing markers to iteritems.
+- compress: make Padme size obfuscation usable ("obfuscate,250,...").
+- borgfs/mount: get_base_dir: avoid using incorrect HOME, #3395.
+
+Other changes:
+
+- PyInstaller binary: do not exclude SSL, needed for pyfuse3/trio, #9196.
+- mount: FUSE FS performance improvement.
+- warn when replaying segments, #9233.
+- CI / tests:
+
+  - build Linux binaries with pyfuse3.
+  - use macOS 15 to build the binaries.
+  - scripts/linux-run: run commands (e.g. tox) in a Podman Linux container.
+  - fix race condition in test_with_lock, #8810.
+  - fix spurious sparse test failure on Win32, #7616.
+  - Cygwin: skip ~root base dir test.
+  - fix coverage collection for daemonized `borg mount`, #9448.
+- docs:
+
+  - move RTD version selector to sidebar top-left, #8204.
+  - consolidate key backup info in `borg key export` help, #6204.
+  - clarify append-only != write-only, #9304.
+  - fix typos found by codespell.
+  - update binary README.
+  - GitHub: enhance pull request template.
+
+
+Version 1.4.3 (2025-12-02)
+--------------------------
+
+New features:
+
+- None.
+
+Fixes:
+
+- compact: replace AssertionError with a warning, #8535.
+- compact: also fix segment hints data for lost segment files.
+- CI: FUSE-related fixes and improvements, #9182:
+
+  - The Linux and FreeBSD binaries built on GitHub now include working
+    FUSE support (based on llfuse).
+  - We can't include FUSE support in the macOS binaries built on GitHub,
+    because we can't install macFUSE there; use our Homebrew tap for that.
+
+Other changes:
+
+- Drop Python 3.9 support (has reached end of life at python.org).
+- CI:
+
+  - Install the correct FUSE library depending on the tox environment.
+  - PyInstaller binary building: build and upload early, then run CI tests.
+  - For now, use llfuse, as there is an issue with PyInstaller and pyfuse3.
+  - Backported vm_tests (FreeBSD/NetBSD/OpenBSD/Haiku) from the master branch.
+  - Dynamic code analysis (Address and Undefined Behavior Sanitizers), #6819.
+  - Add tag-based workflows and provenance attestation for GitHub-built
+    binaries, #9135, #9136.
+- Docs:
+
+  - Some fixes and updates to the FAQ, #9188.
+  - Update binary README; release binaries are built on GitHub now.
+
+
+Version 1.4.2 (2025-10-31)
+--------------------------
+
+New features:
+
 - BORG_MSGPACK_VERSION_CHECK=no to optionally disable the msgpack version
   check; default is "yes"; use at your own risk, #9109.
 - fat binary builds on GitHub (see assets on the GitHub releases page):

{borgbackup-1.4.2 → borgbackup-1.4.4}/docs/conf.py

@@ -161,7 +161,7 @@ smartquotes_action = 'qe'  # no D in there means "do not transform -- and ---"
 
 # Custom sidebar templates, maps document names to template names.
 html_sidebars = {
-    '**': ['logo-text.html', 'searchbox.html', 'globaltoc.html'],
+    '**': ['logo-text.html', "versionselector.html", 'searchbox.html', 'globaltoc.html'],
 }
 
 # Additional templates that should be rendered to pages, maps page names to

{borgbackup-1.4.2 → borgbackup-1.4.4}/docs/development.rst

@@ -185,7 +185,7 @@ Some more advanced examples::
   # verify a changed tox.ini (run this after any change to tox.ini):
   fakeroot -u tox --recreate
 
-  fakeroot -u tox -e py39  # run all tests, but only on python 3.9
+  fakeroot -u tox -e py310  # run all tests, but only on python 3.10
 
   fakeroot -u tox borg.testsuite.locking  # only run 1 test module
 
@@ -304,6 +304,50 @@ Usage::
    # To copy files from the VM (in this case, the generated binary):
    vagrant scp OS:/vagrant/borg/borg.exe .
 
+Using Podman
+------------
+
+macOS-based developers (and others who prefer containers) can run the Linux test suite locally using Podman.
+
+Prerequisites:
+
+-   Install Podman (e.g., ``brew install podman``).
+-   Initialize the Podman machine, only once: ``podman machine init``.
+-   Start the Podman machine, before using it: ``podman machine start``.
+
+Usage::
+
+    # Open an interactive shell in the container (default if no command given):
+    ./scripts/linux-run
+
+    # Run the default tox environment:
+    ./scripts/linux-run tox
+
+    # Run a specific tox environment:
+    ./scripts/linux-run tox -e py311-pyfuse3
+
+    # Pass arguments to pytest (e.g., run specific tests):
+    ./scripts/linux-run tox -e py313-pyfuse3 -- -k mount
+
+    # Switch base image (temporarily):
+    ./scripts/linux-run --image python:3.11-bookworm tox
+
+Resource Usage
+~~~~~~~~~~~~~~
+
+The default Podman VM uses 2GB RAM and half your CPUs.
+For heavy tests (parallel execution), this might be tight.
+
+-   **Check usage:** Run ``podman stats`` in another terminal while tests are running.
+-   **Increase resources:**
+
+    ::
+
+        podman machine stop
+        podman machine set --cpus 6 --memory 4096
+        podman machine start
+
+
 Creating standalone binaries
 ----------------------------
 
@@ -338,7 +382,7 @@ Checklist:
 - Check version number of upcoming release in ``CHANGES.rst``.
 - Render ``CHANGES.rst`` via ``make html`` and check for markup errors.
 - Verify that ``MANIFEST.in``, ``pyproject.toml`` and ``setup.py`` are complete.
-- Run these commands and commit::
+- Run these commands, check git status for files that might need to be added, and commit::
 
     python scripts/make.py build_usage
     python scripts/make.py build_man
@@ -347,6 +391,8 @@ Checklist:
 
     git tag -s -m "tagged/signed release X.Y.Z" X.Y.Z
 
+- Push the release PR branch to GitHub, make a pull request.
+- Also push the release tag.
 - Create a clean repo and use it for the following steps::
 
     git clone borg borg-clean
@@ -355,8 +401,9 @@ Checklist:
   It will also reveal uncommitted required files.
   Moreover, it makes sure the vagrant machines only get committed files and
   do a fresh start based on that.
-- Run tox and/or binary builds on all supported platforms via vagrant,
-  check for test failures.
+- Optional: run tox and/or binary builds on all supported platforms via vagrant,
+  check for test failures. This is now optional as we do platform testing and
+  binary building on GitHub.
 - Create sdist, sign it, upload release to (test) PyPi:
 
   ::
@@ -367,12 +414,13 @@ Checklist:
 
   Note: the signature is not uploaded to PyPi any more, but we upload it to
   github releases.
-- Put binaries into dist/borg-OSNAME and sign them:
-
-  ::
-
-    scripts/sign-binaries 201912312359
 
+- When GitHub CI looks good on the release PR, merge it and then check "Actions":
+  GitHub will create binary assets after the release PR is merged within the
+  CI testing of the merge. Check the "Upload binaries" step on Ubuntu (AMD/Intel
+  and ARM64) and macOS (Intel and ARM64), fetch the ZIPs with the binaries.
+- Unpack the ZIPs and test the binaries, upload the binaries to the GitHub
+  release page (borg-OS-SPEC-ARCH-gh and borg-OS-SPEC-ARCH-gh.tgz).
 - Close the release milestone on GitHub.
 - `Update borgbackup.org
   <https://github.com/borgbackup/borgbackup.github.io/pull/53/files>`_ with the
@@ -388,7 +436,7 @@ Checklist:
   - pypi dist package and signature
   - Standalone binaries (see above for how to create them).
 
-    - For macOS, document the macFUSE version in the README of the binaries.
-      macFUSE uses a kernel extension that needs to be compatible with the
-      code contained in the binary.
+    - For macOS binaries **with** FUSE support, document the macFUSE version
+      in the README of the binaries. macFUSE uses a kernel extension that needs
+      to be compatible with the code contained in the binary.
   - A link to ``CHANGES.rst``.

{borgbackup-1.4.2 → borgbackup-1.4.4}/docs/faq.rst

@@ -210,8 +210,8 @@ sure you have an up-to-date version of borgbackup if you want to continue
 instead of retransferring a huge file. In some cases, there is only an outdated
 version shipped with your distribution (e.g. Debian). See :ref:`installation`.
 
-How can I backup huge file(s) over a unstable connection?
----------------------------------------------------------
+How can I back up huge file(s) over an unstable connection?
+-----------------------------------------------------------
 
 This is not a problem anymore.
 
@@ -381,9 +381,7 @@ Checking processors
   operate hardware outside its specifications for productive use.
 
   Tools to verify correct processor operation include Prime95 (mprime), linpack,
-  and the `Intel Processor Diagnostic Tool
-  <https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool>`_
-  (applies only to Intel processors).
+  and stress-ng.
 
 .. rubric:: Repairing a damaged repository
 
@@ -546,11 +544,10 @@ The Borg config directory has content that you should take care of:
   recovered.
 
 ``keys`` subdirectory
-  All your borg keyfile keys are stored in this directory. Please note that
-  borg repokey keys are stored inside the repository. You MUST make sure to have an
-  independent backup of these keyfiles, otherwise you cannot access your backups anymore if you lose
-  them. You also MUST keep these files secret; everyone who gains access to your repository and has
-  the corresponding keyfile (and the key passphrase) can extract it.
+  All your borg keyfile keys are stored in this directory. Please note that borg
+  repokey keys are stored inside the repository. In any case, you MUST make sure
+  to have an independent backup of the borg keys, see :ref:`borg_key_export` for
+  more details.
 
 Make sure that only you have access to the Borg config directory.
 
@@ -706,7 +703,7 @@ all your files/dirs data and metadata are stored in their encrypted form
 into the repository.
 
 Yes, as an attacker with access to the remote server could delete (or
-otherwise make unavailable) all your backups.
+otherwise make unavailable) all your backups on that server.
 
 How can I protect against a hacked backup client?
 -------------------------------------------------
@@ -743,7 +740,7 @@ These are your options to protect against that:
 How can I protect against theft, sabotage, lightning, fire, ...?
 ----------------------------------------------------------------
 
-In general: if your only backup medium is nearby the backupped machine and
+In general: if your only backup medium is nearby the backed-up machine and
 always connected, you can easily get into trouble: they likely share the same
 fate if something goes really wrong.
 
@@ -796,7 +793,7 @@ Common issues
 There can be many causes of this error. E.g. you have incorrectly specified the repository path.
 
 You will also get this error if you try to access a repository that uses the argon2 key algorithm using an old version of borg.
-We recommend upgrading to the latest stable version and trying again. We are sorry. We should have thought abount forward
+We recommend upgrading to the latest stable version and trying again. We are sorry. We should have thought about forward
 compatibility and implemented a more helpful error message.
 
 Why am I seeing idle borg serve processes on the repo server?
@@ -962,7 +959,7 @@ Then you do the backup and look at the log output:
 
 When borg runs inside a virtual machine, there are some more things to look at:
 
-Some hypervisors (e.g. kvm on proxmox) give some broadly compatible CPU type to the
+Some hypervisors (e.g. kvm on older proxmox) give some broadly compatible CPU type to the
 VM (usually to ease migration between VM hosts of potentially different hardware CPUs).
 
 It is broadly compatible because they leave away modern CPU features that could be
@@ -970,8 +967,8 @@ not present in older or other CPUs, e.g. hardware acceleration for AES crypto, f
 sha2 hashes, for (P)CLMUL(QDQ) computations useful for crc32.
 
 So, basically you pay for compatibility with bad performance. If you prefer better
-performance, you should try to expose the host CPU's misc. hw acceleration features
-to the VM which runs borg.
+performance, you should try to use the x86-64-v2-AES VCPU or the "host" VCPU,
+exposing misc. hw acceleration features to the VM which runs borg.
 
 On Linux, check ``/proc/cpuinfo`` for the CPU flags inside the VM.
 For kvm check the docs about "Host model" and "Host passthrough".
@@ -1295,7 +1292,7 @@ Miscellaneous
 macOS: borg mounts not shown in Finder's side bar
 -------------------------------------------------
 
-https://github.com/osxfuse/osxfuse/wiki/Mount-options#local
+https://github.com/macfuse/macfuse/wiki/Mount-options#local
 
 Read the above first and use this on your own risk::
 
@@ -1415,7 +1412,7 @@ There are some caveats:
 Why is my backup bigger than with attic?
 ----------------------------------------
 
-Attic was rather unflexible when it comes to compression, it always
+Attic was rather inflexible when it comes to compression, it always
 compressed using zlib level 6 (no way to switch compression off or
 adjust the level or algorithm).
 

{borgbackup-1.4.2 → borgbackup-1.4.4}/docs/installation.rst

@@ -158,7 +158,7 @@ To install Borg from a source package (including pip), you have to install the
 following dependencies first. For the libraries you will also need their
 development header files (sometimes in a separate `-dev` or `-devel` package).
 
-* `Python 3`_ >= 3.9.0
+* `Python 3`_ >= 3.10.0
 * OpenSSL_ >= 1.0.0
 * libacl_ (which depends on libattr_)
 * libxxhash_ >= 0.8.1
@@ -424,9 +424,9 @@ If you need to use a different version of Python you can install this using ``py
 
     ...
     # create a virtual environment
-    pyenv install 3.9.0  # minimum, preferably use something more recent!
-    pyenv global 3.9.0
-    pyenv local 3.9.0
+    pyenv install 3.10.0  # minimum, preferably use something more recent!
+    pyenv global 3.10.0
+    pyenv local 3.10.0
     virtualenv --python=${pyenv which python} borg-env
     source borg-env/bin/activate   # always before using!
     ...

{borgbackup-1.4.2 → borgbackup-1.4.4}/docs/internals/data-structures.rst

@@ -818,7 +818,7 @@ bucket is reached.
 This particular mode of operation is open addressing with linear probing.
 
 When the hash table is filled to 75%, its size is grown. When it's
-emptied to 25%, its size is shrinked. Operations on it have a variable
+emptied to 25%, its size is shrunk. Operations on it have a variable
 complexity between constant and linear with low factor, and memory overhead
 varies between 33% and 300%.
 

{borgbackup-1.4.2 → borgbackup-1.4.4}/docs/man/borg-benchmark-crud.1

@@ -1,4 +1,5 @@
-.\" Man page generated from reStructuredText.
+.\" Man page generated from reStructuredText
+.\" by the Docutils 0.22.4 manpage writer.
 .
 .
 .nr rst2man-indent-level 0
@@ -27,8 +28,8 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
-.TH "BORG-BENCHMARK-CRUD" "1" "2025-10-31" "" "borg backup tool"
-.SH NAME
+.TH "borg-benchmark-crud" "1" "2026-03-18" "" "borg backup tool"
+.SH Name
 borg-benchmark-crud \- Benchmark Create, Read, Update, Delete for archives.
 .SH SYNOPSIS
 .sp
@@ -95,7 +96,6 @@ path where to create benchmark input data
 .SH SEE ALSO
 .sp
 \fIborg\-common(1)\fP
-.SH AUTHOR
+.SH Author
 The Borg Collective
-.\" Generated by docutils manpage writer.
-.
+.\" End of generated man page.