Package: borgbackup Version: 1.1.9-2 Severity: important Tags: upstream patch
Dear Maintainer, I've been experiencing index corruption with both, version 1.1.9-2 (Buster) and 1.0.9-1 (Stretch). The issue has been reported upstream [1] and fixed in the 1.1.11 release [2]. In addition, upstream has published some details about the issue [3]. Since data corruption and loss are possible, please consider backporting the fix. Fix for 1.0 series: https://github.com/borgbackup/borg/commit/7bb90b6a513a1d9f951c4883928945f02e814144 Fix for 1.1 series: https://github.com/borgbackup/borg/commit/701159ac9da37d23b8079ebac8f87108c9e550da Many thanks Peter [1]: https://github.com/borgbackup/borg/issues/4829 [2]: https://borgbackup.readthedocs.io/en/stable/changes.html#version-1-1-11-2020-03-08 [3]: https://borgbackup.readthedocs.io/en/stable/changes.html#pre-1-1-11-potential-index-corruption-data-loss-issue -- System Information: Debian Release: 10.3 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.5.8-1.qubes.x86_64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages borgbackup depends on: ii fuse 2.9.9-1 ii libacl1 2.2.53-4 ii libb2-1 0.98.1-1 ii libc6 2.28-10 ii liblz4-1 1.8.3-1 ii libssl1.1 1.1.1d-0+deb10u2 ii libzstd1 1.3.8+dfsg-3 ii python3 3.7.3-1 ii python3-llfuse 1.3.6+dfsg-1 ii python3-msgpack 0.5.6-1+b1 ii python3-pkg-resources 40.8.0-1 borgbackup recommends no packages. Versions of packages borgbackup suggests: pn borgbackup-doc <none> -- no debconf information
