Your message dated Sun, 06 Jul 2008 13:37:06 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#489326: need to be su to run duplicity
has caused the Debian Bug report #489326,
regarding duplicity: encrypt-key, sign-key option error
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.)
--
489326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489326
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Subject: duplicity: encrypt-key, sign-key option error
Package: duplicity
Version: 0.4.11-2
Severity: important
*** Please type your report below this line ***
Hello,
I tested to balkup a file using the --encrypt key and the --sign-key
option and it doesn't work, I got the following error message
I used the same key for encrypt and sign
>duplicty --encrypt-key "XXXXX" --sign-key "XXXXX" t5.txt
file:///tmp/backuptest2
GnuPG passphrase:
Retype to confirm:
No signatures found, switching to full backup.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 463, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 458, in with_tempdir
fn()
File "/usr/bin/duplicity", line 449, in main
full_backup(col_stats)
File "/usr/bin/duplicity", line 155, in full_backup
bytes_written = write_multivol("full", tarblock_iter,
globals.backend)
File "/usr/bin/duplicity", line 87, in write_multivol
globals.gpg_profile,globals.volsize)
File "/usr/lib/python2.5/site-packages/duplicity/gpg.py", line 217, in
GPGWriteFile
file.write(data)
File "/usr/lib/python2.5/site-packages/duplicity/gpg.py", line 125, in
write
return self.gpg_input.write(buf)
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages duplicity depends on:
ii gnupg 1.4.6-2.2 GNU privacy guard - a free
PGP rep
ii libc6 2.7-10 GNU C Library: Shared
libraries
ii librsync1 0.9.7-4 rsync remote-delta
algorithm libra
ii python 2.5.2-1 An interactive high-level
object-o
ii python-central 0.6.7 register and build utility
for Pyt
ii python-gnupginterface 0.3.2-9 Python interface to GnuPG
(GPG)
ii python-pexpect 2.1-1 Python module for
automating inter
duplicity recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 05 Jul 2008 14:32:34 -0400, Feydreva writes:
>gpg directory can only be accessed by root, and to run the gpg command, you
>need to be su, or do a sudo.
if you're using a key that lives in root's keyring, yes: only root has
access to that, just as expected.
but access permissions like that are not a problem of duplicity,
duplicity can't do anything about such a setup and saying
"duplicity: you must be root, period" is not correct in many cases either.
>If I run
...
>Duplicity work fine and I have no error.
i'm closing this bug.
regards
az
--
+ Alexander Zangerl + DSA 42BD645D + (RSA 5B586291)
#define sizeof(x) rand() -- Dark_Brood
signature.asc
Description: Digital Signature
--- End Message ---
