Release 2.0.0b24

[ThomasWaldmann]

See the changelog for what changed in this release.

Installation

pip install borgbackup==2.0.0b24, or use one of the standalone binaries below - they contain everything they need and just have to be made executable.

For each platform there is a single-file binary (borg-*-gh, .exe on Windows) and, as a .tgz, the same thing as a directory (borg-dir/borg.exe), which starts up faster.

The macOS binaries are built without FUSE support, so borg mount does not work with them; install via pip instead if you need FUSE support.

All release assets have a build provenance attestation, verifiable with gh attestation verify --owner borgbackup <file>.

Every attestation is additionally attached as a sigstore bundle <asset>.sigstore.jsonl, so it can be verified offline and without a GitHub token, e.g. with cosign:

cosign verify-blob borgbackup-2.0.0b24.tar.gz \
  --bundle borgbackup-2.0.0b24.tar.gz.sigstore.jsonl \
  --certificate-identity https://github.com/borgbackup/borg/.github/workflows/release.yml@refs/tags/2.0.0b24 \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

The binaries are built by ci.yml, not by release.yml, so their --certificate-identity is https://github.com/borgbackup/borg/.github/workflows/ci.yml@refs/tags/2.0.0b24.

---

This discussion was created from the release Release 2.0.0b24.

[cgroves1]

Is it possible to provide a binary that works on systems with earlier GLIBC support?

I've been testing Borg 1.4.4 and then 1.4.5 on my Synology DS220+ NAS to convert a 8TB (970 TB logical) HyperBackup dataset into several Borg repos with different chunker settings for each repo. This takes about 14 days per repo to process the 402 archives using a common bind mount for Borg's file-cache to skip existing files.

I'd like to start testing Borg 2.0.0b24 on this dataset soon, but the Synology NAS OS (DSM 7.3.2 - Kernel 4.4.302+) only has support for up to GLIBC 2.36.

edit: I'm looking into trying Borg 2.0.0b24 in a docker container to bypass the GLIBC issue, but I'm expecting the performance to be even worse than native.

[ThomasWaldmann]

No (at least not easily), because b24+ also requires OpenSSL >= 3.2 and thus we need to do the Linux builds on Ubuntu 26.04.

b23 did not have that requirement, you can use that for testing.

[bbx0]

You can give my container-borgbackup images a spin, if you like. They are already updated to 2.0.0b24.

docker run -it --rm --read-only --name borg ghcr.io/bbx0/borgbackup:2.0.0b24 benchmark cpu

[cgroves1]

No (at least not easily), because b24+ also requires OpenSSL >= 3.2 and thus we need to do the Linux builds on Ubuntu 26.04.

b23 did not have that requirement, you can use that for testing.

That makes sense. I've managed to get b24 working on a Proxmox system using an Ubuntu 26.04 LXC and am about to try the Docker solution from @bbx0 on the Synology NAS.

[bbx0]

Thanks for including the sigstore bundle so quickly!

$ cosign verify-blob --bundle borgbackup-2.0.0b24.tar.gz.sigstore.jsonl --certificate-identity 'https://github.com/borgbackup/borg/.github/workflows/release.yml@refs/tags/2.0.0b24' --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' borgbackup-2.0.0b24.tar.gz
Verified OK

$ cosign verify-blob-attestation --type slsaprovenance1 --bundle borgbackup-2.0.0b24.tar.gz.sigstore.jsonl --certificate-identity 'https://github.com/borgbackup/borg/.github/workflows/release.yml@refs/tags/2.0.0b24' --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' borgbackup-2.0.0b24.tar.gz
Verified OK

$ cosign verify-blob --bundle borg-linux-glibc243-x86_64-gh.sigstore.jsonl --certificate-identity 'https://github.com/borgbackup/borg/.github/workflows/ci.yml@refs/tags/2.0.0b24' --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' borg-linux-glibc243-x86_64-gh
Verified OK

The binaries are built by ci.yml, not by release.yml, so their --certificate-identity is https://github.com/borgbackup/borg/.github/workflows/ci.yml@refs/tags/2.0.0b24.

--certificate-identity-regexp '^https://github\.com/borgbackup/borg/\.github/workflows/(ci|release)\.yml@refs/tags/2\.0\.0b24$' works for both, if anyone ever needs it.