Your message dated Sat, 29 Nov 2025 14:41:57 +1000
with message-id <[email protected]>
and subject line duplicity ancient bug housecleaning
has caused the Debian Bug report #563418,
regarding duplicity cannot cope with moved 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.)
--
563418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563418
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: duplicity
Version: 0.6.06-2~bpo50+2
Hi,
while trying out duplicity, I ran across the issue that I cannot move
my backup without getting an python exception:
aba@alius:~/DUPL$ mkdir source target
aba@alius:~/DUPL$ touch source/1
aba@alius:~/DUPL$ duplicity full source/ file:///home/aba/DUPL/target/1
--no-encryption
Last full backup date: none
--------------[ Backup Statistics ]--------------
StartTime 1262461299.99 (Sat Jan 2 19:41:39 2010)
EndTime 1262461300.08 (Sat Jan 2 19:41:40 2010)
ElapsedTime 0.09 (0.09 seconds)
SourceFiles 2
SourceFileSize 4096 (4.00 KB)
NewFiles 2
NewFileSize 4096 (4.00 KB)
DeletedFiles 0
ChangedFiles 0
ChangedFileSize 0 (0 bytes)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 2
RawDeltaSize 0 (0 bytes)
TotalDestinationSizeChange 126 (126 bytes)
Errors 0
-------------------------------------------------
aba@alius:~/DUPL$ duplicity list-current-files file:///home/aba/DUPL/target/1
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Sat Jan 2 19:41:39 2010
Sat Jan 2 19:41:29 2010 .
Sat Jan 2 19:34:01 2010 1
aba@alius:~/DUPL$ cp -a target/1 target/2
aba@alius:~/DUPL$ duplicity list-current-files file:///home/aba/DUPL/target/2
Synchronizing remote metadata to local cache...
Copying duplicity-full-signatures.20100102T194139Z.sigtar to local cache.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1236, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1229, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1130, in main
sync_archive()
File "/usr/bin/duplicity", line 947, in sync_archive
copy_to_local(fn)
File "/usr/bin/duplicity", line 899, in copy_to_local
fileobj = globals.backend.get_fileobj_read(rem_name)
File "/usr/lib/python2.5/site-packages/duplicity/backend.py", line 449, in
get_fileobj_read
self.get(filename, tdp)
File "/usr/lib/python2.5/site-packages/duplicity/backends/localbackend.py",
line 62, in get
local_path.writefileobj(source_path.open("rb"))
File "/usr/lib/python2.5/site-packages/duplicity/path.py", line 515, in open
result = open(self.name, mode)
IOError: [Errno 2] No such file or directory:
'/home/aba/DUPL/target/2/duplicity-full-signatures.20100102T194139Z.sigtar.gpg'
aba@alius:~/DUPL$
I can verify that there is no sigtar in neither location.
Cheers,
Andi
--- End Message ---
--- Begin Message ---
as far as i can tell these 10+ year old bugs are closable,
because they're either no longer relevant (pretty different OS environment),
or never received the requested moreinfo followup,
or were not directly related to duplicity itself (ie. applied
to various dependencies),
or were fixed at some point in the past 10+ years without me noting.
regards
az
--
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + https://snafu.priv.at/
Es ist nichts so absurd, daß Gläubige es nicht glaubten.
Oder Beamte täten. -- Arno Schmidt
signature.asc
Description: Digital Signature
--- End Message ---
