Your message dated Sat, 18 Jul 2026 06:49:02 +0000
with message-id <[email protected]>
and subject line Bug#977546: fixed in duplicity 3.1.0-1
has caused the Debian Bug report #977546,
regarding duplicity: remove-all-but-n-full includes failed backups
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
977546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977546
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: duplicity
Version: 0.8.17-1+b1
Severity: normal
X-Debbugs-Cc: none, Barak A. Pearlmutter <[email protected]>
I ran out of storage on my remote, so I tried to reclaim some with
$ duplicity remove-all-but-n-full 1 --force "${transport}/${target}"
But afterwards there are just a few meg used in the target directory
instead of many hundreds of gig. It would appear that a full backup
failed due to space exhaustion on the remote, but that the failed full
backup is (inappropriately) included in remove-all-but-n-full's count.
This is just my best guess as to what's going on. But I am 100% sure
that "duplicity remove-all-but-n-full 1" sometimes does not leave an
intact full backup, instead it deletes nearly everything.
This has happened to me repeatedly, so I'm sure there's an actual
problem.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (490, 'testing'), (450, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages duplicity depends on:
ii gnupg 2.2.20-1
ii libc6 2.31-5
ii librsync2 2.3.1-1
ii python3 3.9.0-4
ii python3-fasteners 0.14.1-2
ii python3-future 0.18.2-4
ii python3-lockfile 1:0.12.2-2.2
Versions of packages duplicity recommends:
pn python3-oauthlib <none>
ii python3-paramiko 2.7.2-1
ii python3-pexpect 4.6.0-4
ii python3-urllib3 1.25.11-1
ii rsync 3.2.3-2
Versions of packages duplicity suggests:
pn lftp <none>
pn ncftp <none>
pn par2 <none>
pn python3-boto <none>
ii python3-pip 20.1.1-2
pn python3-swiftclient <none>
pn tahoe-lafs <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: duplicity
Source-Version: 3.1.0-1
Done: Alexander Zangerl <[email protected]>
We believe that the bug you reported is fixed in the latest version of
duplicity, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alexander Zangerl <[email protected]> (supplier of updated duplicity 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 18 Jul 2026 16:14:06 +1000
Source: duplicity
Architecture: source
Version: 3.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Alexander Zangerl <[email protected]>
Changed-By: Alexander Zangerl <[email protected]>
Closes: 977546 1120839
Changes:
duplicity (3.1.0-1) unstable; urgency=medium
.
* new upstream release (closes: #1120839, #977546)
Checksums-Sha1:
cce13d2e983a540679802a2cdddb5d0ca39fe3e4 2021 duplicity_3.1.0-1.dsc
b967bcd8692ac48bbd27f59b8920f0a1ab4d1055 996110 duplicity_3.1.0.orig.tar.bz2
f435ce57f7c0d6bef6ba06e8fe24e36581d9f77a 18452 duplicity_3.1.0-1.debian.tar.xz
1309837d7a1f9d71ad231af9651f90cfe96d6a00 10709
duplicity_3.1.0-1_amd64.buildinfo
Checksums-Sha256:
a54b0cd45720792f78a6b68409f9f81e776368a267346aae4e75548a06bcaca2 2021
duplicity_3.1.0-1.dsc
d52aa71cc841990ab2337bc224482f8702b08f269a4f1f5fdaadc679a0207406 996110
duplicity_3.1.0.orig.tar.bz2
90f044217517b1c3978e6dd43c20df594fa7fb559abed09b39b80a2477760da3 18452
duplicity_3.1.0-1.debian.tar.xz
301e124d6ee07eda77d1533da6b63b47837efeb8b68645d5f3e1cc4b32b71f31 10709
duplicity_3.1.0-1_amd64.buildinfo
Files:
34263d3841445e3d723dccb8ff5e36fc 2021 utils optional duplicity_3.1.0-1.dsc
3809a45869683d0ccdda2f2efb88f03b 996110 utils optional
duplicity_3.1.0.orig.tar.bz2
c49cf7230e8db69ac7e8761676cd2ce5 18452 utils optional
duplicity_3.1.0-1.debian.tar.xz
f17b27b9b21917473a15de9ee5880ca9 10709 utils optional
duplicity_3.1.0-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJqWx0XAAoJED06g4g30PqNG/AP/iavh87KoN/QVgd6n1gFRIdO
8gTeAuJi7So/dXWljoi2YfPVAxXXpYae2kqmfqxsmGTVTXjRpaQUIyZxxLZxaEd6
an0TORrHkPDxnVGxks++mjTedyj9866Tum5fa6zuKk8wqNCHrti0Pfnjg7ko5RE8
1Awg7Iq22b7XrNTV7OU0kPLZ//Gd+Hyc1xHO0+vD5VkEO2gC61dTDGXWw33ccRxy
pwnBOSUn0Plix6FuTtgYPbnEfsIOKcyzzmkIXdi6L9kOj3b+/JBJOnM80QxyunTi
B9VZitgpN8j5n3pW18YNRpqLAgzn6spFVyFFeXdBGtzHKX/bh7vE0scrHjp1xcWy
083YuLKNnG/I3033jPvBBxkcMCd1kCIr/QoSVbeBspdVNo8uIN6USmWsFwzi+T/Y
DyYITzFep19iSLqBJg54sXQfVUM2UEUi1BPnl4WRyTKuOj0v3j+ASXGXmwcEtOx8
mSMTvUcC6xXvTVS3HFxc7OrsynuYUa30mbDrHj9+Ds1M7ppYUZAlHSfixRyOcLIF
mjIEoJGM+YStBat2qUcEB9NXQ6bNP9GFPDpLvSebMfc1o06uQjSOGXFGcKDetzmy
XIvOyxNVZMHfrs663TPr8AurfyeepzSE7CpDvLEDrFU5TaXa0CImy6YksXt0gNZJ
9Pi7sWtxVwW27b3SA8Y/
=THyD
-----END PGP SIGNATURE-----
pgp81PVjllGgD.pgp
Description: PGP signature
--- End Message ---
