Package: borgbackup Version: 1.1.4-3 Followup-For: Bug #893972 I can still reproduce this bug with 1.1.4-3. I have python3-msgpack/0.5.1-3 installed, although borgbackup does not currently depend on it (probably also a bug).
This looks like fallout from <https://bugs.debian.org/893844>, where Adrian Bunk wrote: > This has now been fixed in python3-msgpack, and borgbackup in unstable > [will] pick up the fix through a rebuild soon. Hopefully a binNMU on all architectures will be sufficient to fix this. Workaround (which is the reason why reportbug reports a debsums mismatch): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893844#10 > Quick and extremely dirty workaround: > > Edit > /usr/lib/python3/dist-packages/borgbackup-1.1.4.egg-info/requires.txt > and change "msgpack-python" to just "msgpack". I confirm that the workaround is successful. Thanks, smcv -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (100, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (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.7-1 ii libacl1 2.2.52-3+b1 ii libb2-1 0.97+git20171226-2 ii libc6 2.27-2 ii liblz4-1 0.0~r131-2+b1 ii libssl1.1 1.1.0g-2 ii libzstd1 1.3.3+dfsg-1 ii python3 3.6.5~rc1-1 ii python3-llfuse 1.3.2+dfsg-2 ii python3-pkg-resources 39.0.1-1 borgbackup recommends no packages. Versions of packages borgbackup suggests: pn borgbackup-doc <none> -- no debconf information -- debsums errors found: debsums: changed file /usr/lib/python3/dist-packages/borgbackup-1.1.4.egg-info/requires.txt (from borgbackup package)
