group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <2125904@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package borgbackup - 1.2.0-1ubuntu1.22.04.1

---------------
borgbackup (1.2.0-1ubuntu1.22.04.1) jammy; urgency=medium

  * debian/patches/6769.patch:
    - cherry-pick upstream patch to fix a db corruption possible issue
      (LP: #2125904)

 -- Gianfranco Costamagna <locutusofborg@xxxxxxxxxx>  Mon, 29 Sep 2025
09:18:27 +0200

** Changed in: borgbackup (Ubuntu Jammy)
       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/2125904

Title:
  [SRU] borgbackup in jammy might loose backup in some corner cases

Status in borgbackup package in Ubuntu:
  Fix Released
Status in borgbackup source package in Trusty:
  Invalid
Status in borgbackup source package in Xenial:
  Invalid
Status in borgbackup source package in Bionic:
  Won't Fix
Status in borgbackup source package in Focal:
  Won't Fix
Status in borgbackup source package in Jammy:
  Fix Released
Status in borgbackup source package in Noble:
  Fix Released
Status in borgbackup source package in Plucky:
  Fix Released
Status in borgbackup source package in Questing:
  Fix Released

Bug description:
  [ Impact ]
  [ from https://github.com/borgbackup/borg/issues/6768 ]
  Full borg commandline that lead to the problem (leave away excludes and passwords)

  
  [ Test Plan ]
  mkdir /tmp/borgtest
  cd /tmp/borgtest
  borg init -e none test.repo
  cp -al test.repo copy.repo
  borg check -v test.repo
  cat copy.repo/config  [binary data]

  After making a hardlink copy of a repo, running check on the original causes corruption of the config file in the copy. It happens with archives in the repo too, but I omitted this to make the script as short as possible.
  Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.

  Reproducible using the steps above.
  Include any warning/errors/backtraces from the system logs

  [ Where problems could occur ]
  * During backup/restore of databases

  [ Other Info ]
  * This is an upstream fix backported to jammy.

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