- Package:
- src:borgbackup
- Source:
- src:borgbackup
- Submitter:
- Date:
- 2026-07-07 01:35:02 UTC
- Severity:
- normal
- Tags:
Dear maintainer, According to https://ci.debian.net data, your package borgbackup has an autopkgtest regression with pytest. The following architectures failed: amd64, arm64, i386, loong64, ppc64el, riscv64, s390x. Hopefully relevant excerpt from https://ci.debian.net/packages/b/borgbackup/testing/amd64/72539238/ follows: 927s =================================== FAILURES =================================== 927s E AssertionError: assert 'Extracting:' in '' 927s E AssertionError: '\r' not found in '0 B O 0 B C 0 B D 0 N input\n\n' 927s E AssertionError: 'Checking segments' not found in 'Starting repository check\nfinished segment check at segment 9\nStarting repository index check\nIndex object count match.\nFinished full repository check, no problems found.\nStarting archive consistency check...\nAnalyzing archive archive1 (1/2)\nAnalyzing archive archive2 (2/2)\nArchive consistency check complete, no problems found.\n' 927s E AssertionError: assert 'Extracting:' in '' 927s E AssertionError: assert '' == ' 0%\r' 927s E 927s E - 0% 927s E AssertionError: assert '' == ' 0% スター・トレッ...ーク船長です。 \r' 927s E 927s E - 0% スター・トレック /カーク船長です。 927s E AssertionError: assert '' == ' 0%\r' 927s E 927s E - 0% 927s E AssertionError: '\r' not found in '0 B O 0 B C 0 B D 0 N input\n\n' 928s ===== 8 failed, 1534 passed, 158 skipped, 4 warnings in 827.97s (0:13:47) ====== 930s unit FAIL non-zero exit status 1 1733s =================================== FAILURES =================================== 1733s E AssertionError: assert 'Extracting:' in '' 1733s E AssertionError: '\r' not found in '0 B O 0 B C 0 B D 0 N input\n\n' 1733s E AssertionError: 'Checking segments' not found in 'Starting repository check\nfinished segment check at segment 9\nStarting repository index check\nIndex object count match.\nFinished full repository check, no problems found.\nStarting archive consistency check...\nAnalyzing archive archive1 (1/2)\nAnalyzing archive archive2 (2/2)\nArchive consistency check complete, no problems found.\n' 1733s E AssertionError: assert 'Extracting:' in '' 1733s E AssertionError: assert '' == ' 0%\r' 1733s E 1733s E - 0% 1733s E AssertionError: assert '' == ' 0% スター・トレッ...ーク船長です。 \r' 1733s E 1733s E - 0% スター・トレック /カーク船長です。 1733s E AssertionError: assert '' == ' 0%\r' 1733s E 1733s E - 0% 1733s E AssertionError: '\r' not found in '0 B O 0 B C 0 B D 0 N input\n\n' 1733s ===== 8 failed, 1514 passed, 178 skipped, 3 warnings in 714.80s (0:11:54) ====== 1735s unit-nofuse FAIL non-zero exit status 1 1893s unit FAIL non-zero exit status 1 1893s unit-nofuse FAIL non-zero exit status 1
Control: unmerge 1140857
Control: retitle 1140857 borgbackup: FTBFS and autopkgtest failures related to output/logging
Control: tags 1140857 + fixed-upstream patch
[which also led to a FTBFS]
I found an upstream commit (not in a release yet) that seems to
successfully address these 8 build-time test failures, which are all
related to making assertions about borg's logging/progress/diagnostic
output:
FAILED borg/testsuite/archiver.py::ArchiverTestCase::test_extract_progress - ...
FAILED borg/testsuite/archiver.py::ArchiverTestCase::test_progress_on - Asser...
FAILED borg/testsuite/archiver.py::ArchiverCheckTestCase::test_check_usage - ...
FAILED borg/testsuite/archiver.py::RemoteArchiverTestCase::test_extract_progress
FAILED borg/testsuite/archiver.py::RemoteArchiverTestCase::test_progress_on
FAILED borg/testsuite/helpers.py::test_progress_percentage_sameline - Asserti...
FAILED borg/testsuite/helpers.py::test_progress_percentage_widechars - Assert...
FAILED borg/testsuite/helpers.py::test_progress_percentage_step - AssertionEr...
That leaves two more test failures, related to setxattr
security.capabilities while running under fakeroot:
FAILED borg/testsuite/archiver.py::ArchiverTestCase::test_extract_capabilities
FAILED borg/testsuite/archiver.py::RemoteArchiverTestCase::test_extract_capabilities
which Santiago Vila had reported as #1137392, before the additional
regressions that were first reported in #1140857.
So let's unmerge #1137392 from #1140857 (they were previously merged by
Andrey Rakhmatullin) and use #1140857 to represent the 8 newer
logging-related failures, and #1137392 to represent the 2 older
test_extract_capabilities failures. Both bugs need to be resolved before
borgbackup will pass tests again.
Please see attached for what appears to be the upstream solution to
#1140857.
I also sent a workaround to #1137392 (disabling the use of fakeroot to
run unit tests). Combining that workaround with the upstream patch
attached here should hopefully be enough to get borgbackup compiling
again, although with reduced test coverage.
Thanks,
smcv
Hello, Simon McVittie <smcv@debian.org> writes: #1137392 appears to have been a fakeroot regression, and I'm happy we waited instead of reducing borgbackup's test coverage. I've applied the patch you cherry picked and my system is half way through the tests. It looks to me like this is required adaptation to pytest changes, and that it will be in the next patch-level upstream release. In other words, lets expect success! Cheers, Nicholas
We believe that the bug you reported is fixed in the latest version of
borgbackup, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1140857@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nicholas D Steeves <sten@debian.org> (supplier of updated borgbackup package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 06 Jul 2026 20:46:44 -0400
Source: borgbackup
Architecture: source
Version: 1.4.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Borg Collective <team+borg@tracker.debian.org>
Changed-By: Nicholas D Steeves <sten@debian.org>
Closes: 1140857
Changes:
borgbackup (1.4.4-4) unstable; urgency=medium
.
* Team upload.
* Cherry pick tests-reset-borg.output.progress-logger-between-tests-to-.patch
from upstream to resolve the regression with pytest 9.1 (Closes: #1140857),
thanks to Simon McVittie.
Checksums-Sha1:
1d7bd133d8b739d881a524fb865ba73db0c378f7 3039 borgbackup_1.4.4-4.dsc
5af23aa8bdac2bb5fa33dcc30d25738227e533d2 25256 borgbackup_1.4.4-4.debian.tar.xz
f68bd3cfcd898d3ea911703e03caa24e528ac59f 9963 borgbackup_1.4.4-4_amd64.buildinfo
Checksums-Sha256:
a6f61585a0416d909cf0d69437d4a1aee13bdbb222df4f93b08ce0235118cf45 3039 borgbackup_1.4.4-4.dsc
bbff17de684dcd6df2a0dace8bc34ca880c9b625d9ce9bb7922382c7701c0da7 25256 borgbackup_1.4.4-4.debian.tar.xz
509cabb97c6aa41f7b8f1cc9b216ef6b7dd0302754b52dadd3f44ace3060ddee 9963 borgbackup_1.4.4-4_amd64.buildinfo
Files:
d4df5edaaa867f8e1a325d88b760c7b6 3039 admin optional borgbackup_1.4.4-4.dsc
1e3a8d36df8e41eb511f8ddf5d688367 25256 admin optional borgbackup_1.4.4-4.debian.tar.xz
57d374e809110f3926f406b58ca86e61 9963 admin optional borgbackup_1.4.4-4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmpMU88ACgkQWogwR199
EGEkSBAA1+VtsCOJ6yp3b8SUqk6nAE1qDUkCG4YocYBTlHRS9+v8qhatQN65uJkc
klJ1G8WNRYyGwppyCmPsWmC4tayyEK9O8q+h2yNjEmcDkGxLYqH0rPBjjxKGtvcc
hDmFQm7vlwzdYlwpw2TNNuuBpL88EVzc5m61dZtr9hYpoRITBijcir4nwoSC3JWu
XuzA3y4ukvP7fFvIhyNZvh29UVzR9UR6qUKjR+tclNLjEdsFRrUNuuwWJP3yfOEE
q99Q+UUyIsbd8qVlf+HpYlirDOi8RCjTi9WuTP7AwdP2bkhsuowibDww3Lzyp5Ei
I3S/ZSvUoi5yBNpfQqaWKi1ejoZBCqFm5SXl8IIxSXxCguRgxXYElD9U+YvIoEYB
YH7Ve7QoURSJj/jdZojS7DUmHchVFdktH94ybHq57mCirwRrwD5rFlYAv3GdiN58
5ih9MBPxnraKwupqFaVRqD0b7qbIcbhYc8f/ZVui4bXI5OT8Jx6CfTe3rtb8W/GX
qqrn0osxIUTB/QqEjPQ62AB1NCYR+QKYBt/v6qw9+sX8y/Xn4em4MWtYmdcFJyHh
M0a3zH/vYurBhTCXCOe61XH/6iNjFXz1AusHnE/aLidoBtMg1nue4ulSo1r/Qd7o
9XOFPDYoEpnWKuq1x3NxS9lOtrLl7LDdtroEcSt00XxbkPpsF6o=
=6KTu
-----END PGP SIGNATURE-----