Your message dated Tue, 17 Jan 2012 10:22:40 +1000
with message-id <[email protected]>
and subject line Re: Bug#640315: duplicity: spits strange error: Unable to
delete .gpg files in ~/.cache directory
has caused the Debian Bug report #640315,
regarding duplicity: spits strange error: Unable to delete .gpg files in
~/.cache directory
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.)
--
640315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640315
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: duplicity
Version: 0.6.14-1
Severity: normal
Hi!
Thanks for maintaining duplicity in Debian!
I've recently noticed this error on another box, but now I managed to
copy the exact error message.
After issuing the following command (as regular user):
$ duplicity --encrypt-key $MYGPGKEY --full-if-older-than 30D \
--include-globbing-filelist .duplicity.include . file://backup
I obtained the following error message, just after the local
cache synchronization, but before the statistics table:
Unable to delete
/home/$MYUSERNAME/.cache/duplicity/4ae0b7093d93097164a8831bfad7f9c8/duplicity-new-signatures.20110828T071808Z.to.20110904T082028Z.sigtar.gpg:
[Errno 2] No such file or directory:
'/home/$MYUSERNAME/.cache/duplicity/4ae0b7093d93097164a8831bfad7f9c8/duplicity-new-signatures.20110828T071808Z.to.20110904T082028Z.sigtar.gpg'
Unable to delete
/home/$MYUSERNAME/.cache/duplicity/4ae0b7093d93097164a8831bfad7f9c8/duplicity-inc.20110828T071808Z.to.20110904T082028Z.manifest.gpg:
[Errno 2] No such file or directory:
'/home/$MYUSERNAME/.cache/duplicity/4ae0b7093d93097164a8831bfad7f9c8/duplicity-inc.20110828T071808Z.to.20110904T082028Z.manifest.gpg'
It seems that duplicity attempts to delete these two files, but cannot,
as they do not exist.
Actually my local cache directory includes a number of files, among which
/home/$MYUSERNAME/.cache/duplicity/4ae0b7093d93097164a8831bfad7f9c8/duplicity-new-signatures.20110828T071808Z.to.20110904T082028Z.sigtar.gz
/home/$MYUSERNAME/.cache/duplicity/4ae0b7093d93097164a8831bfad7f9c8/duplicity-inc.20110828T071808Z.to.20110904T082028Z.manifest
but no .gpg file lives in the local cache (as I understand it, this
is correct and expected).
Hence, I fail to understand why duplicity attempts to remove files
that cannot be found where it looks for them.
Is there anything wrong with the command I use to perform my user
data backup?
Is this a bug?
If it is indeed a bug, then please fix it and/or forward it upstream.
Thanks a lot for your time!
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages duplicity depends on:
ii libc6 2.13-16 Embedded GNU C Library: Shared lib
ii librsync1 0.9.7-8 rsync remote-delta algorithm libra
ii python 2.6.7-3 interactive high-level object-orie
ii python-gnupginterface 0.3.2-9.1 Python interface to GnuPG (GPG)
ii python-pexpect 2.3-1 Python module for automating inter
ii python2.6 2.6.7-3 An interactive high-level object-o
duplicity recommends no packages.
Versions of packages duplicity suggests:
pn ncftp <none> (no description available)
pn python-boto <none> (no description available)
ii rsync 3.0.8-1 fast remote file copy program (lik
pn ssh <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, 16 Jan 2012 00:06:04 +0100, Francesco Poli writes:
>It seems to me that this bug has been fixed in Debian testing.
i haven't done anything about this bug in 0.6.17.
>I have no longer seen the error messages I originally reported.
that's good to hear. i've just retested things here, and the bug is
indeed really gone.
>However, it's strange that the upstream bug report has not yet been
>closed.
the upstream changelogs don't show anything obviously related to this
bug...
>Why is the upstream bug report still open?
...so i suppose upstream hasn't realized yet that the problem was fixed
as a side effect of some other unrelated work.
regards
az
--
+ Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291
+ http://snafu.priv.at/
You should never anthropomorphize computers; they hate that. -- Skud
signature.asc
Description: Digital Signature
--- End Message ---
