duplicity-talk
[Top][All Lists]
Advanced

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

Re: [Duplicity-talk] duply/duplicity working directory when using a GOOG


From: edgar . soldin
Subject: Re: [Duplicity-talk] duply/duplicity working directory when using a GOOGLE_DRIVE_SETTINGS file for gdocs/pydrive
Date: Sun, 18 Oct 2015 20:14:32 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0

On 18.10.2015 20:13, Kostas Papadopoulos wrote:
> On 10/17/2015 5:42 PM, address@hidden wrote:
>> try setting 
>>  save_credentials_file: /some/absolute/path/gdrive.cache
>> to keep the auth cache somewhere safe/reusable.
>>
>> to make sure the discovery cache is not left over try to patch your 
>> 'duplicity/tempdir.py' like this
>>  http://bazaar.launchpad.net/~ed.so/duplicity/tempfile.tempdir/revision/1136 
>> <http://bazaar.launchpad.net/%7Eed.so/duplicity/tempfile.tempdir/revision/1136>
>>
>> does that work for you? ..ede
> 
> Hi,
> 
> The proposed change worked for me, I can now run duplicity with gdocs from 
> other dirs,
> however *file google-api-python-client-discovery-doc.cache is still left over 
> in /tmp*:
> 
> Br,
> KP
> 
>     address@hidden:/tmp# ~/bin/duply mytest-oauth status
>     Start duply v1.10.1, time is 2015-10-18 18:01:42.
>     Using profile '/root/.duply/mytest-oauth'.
>     Using installed duplicity version 0.7.05, python 2.7.3, gpg 1.4.12 (Home: 
> ~/.gnupg), awk 'mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan', grep 
> 'grep (GNU grep) 2.12', bash '4.2.37(1)-release (x86_64-pc-linux-gnu)'.
>     Autoset found secret key of first GPG_KEY entry '0841EA59' for signing.
>     Checking TEMP_DIR '/tmp' is a folder (OK)
>     Checking TEMP_DIR '/tmp' is writable (OK)
>     Test - Encrypt to 'xxxxxx' & Sign with 'xxxxxx' (OK)
>     Test - Decrypt (OK)
>     Test - Compare (OK)
>     Cleanup - Delete '/tmp/duply.1412.1445191302_*'(OK)
> 
>     --- Start running command STATUS at 18:01:42.545 ---
>     Local and Remote metadata are synchronized, no sync needed.
>     Last full backup date: Sat Oct 17 20:19:20 2015
>     Collection Status
>     -----------------
>     Connecting with backend: BackendWrapper
>     Archive dir: /root/.cache/duplicity/duply_mytest-oauth
> 
>     Found 0 secondary backup chains.
> 
>     Found primary backup chain with matching signature chain:
>     -------------------------
>     Chain start time: Sat Oct 17 20:19:20 2015
>     Chain end time: Sat Oct 17 21:18:18 2015
>     Number of contained backup sets: 3
>     Total number of contained volumes: 3
>      Type of backup set:                            Time:      Num volumes:
>                     Full         Sat Oct 17 20:19:20 2015                 1
>              Incremental         Sat Oct 17 20:33:32 2015                 1
>              Incremental         Sat Oct 17 21:18:18 2015                 1
>     -------------------------
>     No orphaned or incomplete backup sets found.
>     --- Finished state OK at 18:01:44.774 - Runtime 00:00:02.228 ---
>     address@hidden:/tmp#
> 
> 
>     address@hidden:/tmp# ls -la
>     total 152
>     drwxrwxrwt  2 root root   4096 Oct 18 18:01 .
>     drwxr-xr-x 22 root root   4096 Oct 18 17:53 ..
>     -rw-------  1 root root 144584 Oct 18 18:01 
> google-api-python-client-discovery-doc.cache
>     address@hidden:/tmp#
> 

did you patch tempdir.py? ..ede



reply via email to

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