duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] --no-encryption generates a GPGError ?


From: jb
Subject: Re: [Duplicity-talk] --no-encryption generates a GPGError ?
Date: Sun, 4 Jul 2010 22:55:40 +1000

under 2.3 I got the error
  File "/usr/lib64/python2.3/site-packages/duplicity/commandline.py",
line 157, in DupOption
    ALWAYS_TYPED_ACTIONS = optparse.Option.ALWAYS_TYPED_ACTIONS + ("extend",)
AttributeError: class Option has no attribute 'ALWAYS_TYPED_ACTIONS'

after installing python 2.4 RPM I could not get it to use librsync
(which was installed from another RPM).

    import _librsync
ImportError: /usr/lib/python2.4/site-packages/duplicity/_librsync.so:
cannot open shared object file: No such file or directory

but it was there:
file /usr/lib/python2.4/site-packages/duplicity/_librsync.so
/usr/lib/python2.4/site-packages/duplicity/_librsync.so: ELF 64-bit
LSB shared object, AMD x86-64, version 1 (SYSV), not stripped

so then I just compiled 2.6 and installed it, and everything behaved,
even with the original librsync.

So you are probably right python 2.4 would have worked.

On Sun, Jul 4, 2010 at 9:50 PM, Kenneth Loafman <address@hidden> wrote:
> Will have to fix the 2.3 issue you mentioned.  It should have worked under
> 2.4 though.  What kind of errors did you get?
>
> jb wrote:
>
> Ah thanks that is indeed the case!
>
> An error message like "original backup is encrypted", perhaps :)
>
> thanks,
>
> By the way it would be good if the installer required python 2.6,
> because I wasted a good deal of time trying to get it working under
> python 2.3 (because that is what it told me it needed), then 2.4
> (often people have older linux released and 2.6 RPMs do not
> immediately fall to hand). Finally going to 2.6 from source as a last
> attempt!
>
> On Sun, Jul 4, 2010 at 9:38 PM, Kenneth Loafman <address@hidden> wrote:
>
>
> jb,
>
> From this line:
>
> Last full backup date: Sat Jul  3 02:56:56 2010
>
> I can see that you have an existing full backup, so you're implicitly
> asking for an incremental to be performed.  If the full backup is
> encrypted, then duplicity needs the passphrase in order to do the
> incremental.  Was the full backup encrypted?
>
> ...Ken
>
> jb wrote:
>
>
> (excuse the double mail if that happened, I sent this before
> subscribing to the list and so I am not sure if it made it).
>
>
> Should this not work without error?
>
> same command works ok with encryption.
>
> address@hidden ~]# python -V
> Python 2.6.5
> address@hidden ~]# duplicity --version
> duplicity 0.6.08b
> address@hidden ~]# python -V
> Python 2.6.5
> address@hidden ~]# duplicity --no-encryption /etc s3+http://test_duplicity
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Sat Jul  3 02:56:56 2010
> GPGError: GPG Failed, see log below:
> ===== Begin GnuPG log =====
> gpg: CAST5 encrypted data
> gpg: encrypted with 1 passphrase
> gpg: decryption failed: bad key
> ===== End GnuPG log =====
>
> address@hidden ~]# PASSPHRASE=x duplicity --no-encryption /etc
> s3+http://test_duplicity
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Sat Jul  3 02:56:56 2010
> GPGError: GPG Failed, see log below:
> ===== Begin GnuPG log =====
> gpg: CAST5 encrypted data
> gpg: encrypted with 1 passphrase
> gpg: decryption failed: bad key
> ===== End GnuPG log =====
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]