← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1877844] Re: [SRU] borgbackup version 1.1.15 and 1.0.13

 

This bug was fixed in the package xxhash - 0.7.3-1~ubuntu18.04.2

---------------
xxhash (0.7.3-1~ubuntu18.04.2) bionic; urgency=medium

  * Lower compat level to 11 to let it build with older debhelper
    - LP: #1877844

 -- Gianfranco Costamagna <locutusofborg@xxxxxxxxxx>  Fri, 08 Jan 2021
19:03:49 +0100

** Changed in: borgbackup (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1877844

Title:
  [SRU] borgbackup version 1.1.15 and 1.0.13

Status in borgbackup package in Ubuntu:
  Fix Released
Status in xxhash package in Ubuntu:
  Fix Released
Status in borgbackup source package in Xenial:
  Fix Released
Status in borgbackup source package in Bionic:
  Fix Released
Status in xxhash source package in Bionic:
  Fix Released
Status in borgbackup source package in Focal:
  Fix Released
Status in borgbackup source package in Groovy:
  Fix Released
Status in xxhash source package in Groovy:
  Fix Released
Status in borgbackup package in Debian:
  Fix Released

Bug description:
  [ Impact ]
  * Data is corrupted on some specific conditions, upstream asked to backport 1.1.15 that fixes some high ram usage and this corruption bug (not for focal, already fixed)

  [ Regression Potential ]
  * Really low, the package has an autopkgtestsuite that runs thousand of tests, and the fix is since one year part of upstream code

  [ Test Case ]
  * Backup some TB of data, and try to read the index, it should be not corrupted

  [ Other info ]
  Per the "important notes" section of the borg docs:

  https://borgbackup.readthedocs.io/en/stable/changes.html

  "Pre-1.1.11 potential index corruption / data loss issue
  A bug was discovered in our hashtable code, see issue #4829. The code is used for the client-side chunks cache and the server-side repo index.

  Although borg uses the hashtables very heavily, the index corruption
  did not happen too frequently, because it needed specific conditions
  to happen.

  Data loss required even more specific conditions, so it should be rare
  (and also detectable via borg check). [..]"

  Theoretically affects all Ubuntu releases before 20.04 (focal.)

  I know this is a universe package, but if anyone was up for an SRU
  that would be fantastic..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/borgbackup/+bug/1877844/+subscriptions