Source: borgbackup Version: 1.0.11-3 Severity: normal Please note that the server and the client should be on the same version of borgbackup. Using different versions of borgbackup on client and server might result in 'incompatible API version' error messages and a non-working backup.
Could this happen between any two versions even if only the minor version changed? It's not clear. I found this in the documentation: EXPECT THAT WE WILL BREAK COMPATIBILITY REPEATEDLY WHEN MAJOR RELEASE NUMBER CHANGES (like when going from 0.x.y to 1.0.0 or from 1.x.y to 2.0.0). Which seems to suggest that the API version change would only affect major version number changes, but I'm not clear if it's talking about the same kind of API mismatch. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- see shy jo
signature.asc
Description: PGP signature
