Carlos, just a heads up. just yesterday Ken committed the following changes. - enabling Gdocs access via pydrive:// - making gdocs:// an alias for pydrive:// - keeping the old backend as gdata+gdocs:
Thanks for the explanation. I get the following error: UnsupportedBackendScheme: scheme not supported in url: pydrive2://address@hidden/Backups/Duplicity Here are the pydrive backends that I have (
Done. On Sun, May 31, 2015 at 7:39 AM, <address@hidden> wrote: maybe after you merged lp:~bmerry/duplicity/pydrive-regular ? .ede On 31.05.2015 14:37, Kenneth Loafman wrote: _______________________
this looks like an OAuth w/ gdata example http://stackoverflow.com/questions/16026286/using-oauth2-with-service-account-on-gdata-in-python ..ede/duply.net _________________________________________
this looks like an OAuth w/ gdata example http://stackoverflow.com/questions/16026286/using-oauth2-with-service-account-on-gdata-in-python ..ede/duply.net
afaiu gdocs per se isn't deprecated but it's method of authentication currently used. pydrive2 seems to be an alternative route to access gdocs. please someone correct if i am wrong. ..ede/duply.net
You can use the pydrive backend instead of gdocs. pydrive uses storage associated with a google service account which means you can't access the backups using the Google Drive web interface or access
My duplicity logon to google-docs fails. I am redirected to the web page https://developers.google.com/identity/protocols/AuthForInstalledApps which explains that Important: ClientLogin has been of
A patch is attached for a new backend called pydrive2 which uses user storage, like the (now defunct) gdocs backend and unlike the pydrive backend. To use it: (1) patch -o pydrive2backend.py pydriveb
Hi there, I tried to do the things outlined by Mikko and I can't make it work the way I need to. I cannot activate the virtual environment automatically before running duply/duplicity. So when I use
i would love to only use packaged python scripts, but failed to grasp how this can be combined and kept up-to-date? So far it looks like the pip packages are all ending up in /usr/local/lib and then
Hi Jacob, Hi Mikko, thanks for the warning. Could you please elaborate on this or send me some reading, that describes this conflict? While searching around python, I could not find an explanation wh
Hi Claudio, thanks for sharing, I tried that as well, but it did not help. It was only the updated version that made it work for me. Regards Christian Am Montag, den 27.04.2015, 16:06 +0100 schri
Hi Claudio, thanks for sharing, I tried that as well, but it did not help. It was only the updated version that made it work for me. Regards Christian Am Montag, den 27.04.2015, 16:06 +0100 schri
Hi Claudio, thanks for sharing, I tried that as well, but it did not help. It was only the updated version that made it work for me. Regards Christian Am Montag, den 27.04.2015, 16:06 +0100 schrieb C
Hi, I've been using duplicity 0.6.25 and a Frankfurt bucket as target. The only thing* I needed to do was: export S3_USE_SIGV4="True" * I may have upgraded python-boto (through the system packages) b
Sorry, took a while to put this together. I put up a little Webpage to store this solutions for me. You find it here: sowhatisthesolution.wordpress.com Also, not to be a traffic leech, here the solut
After successfully testing duplicity on one of our workstations, it seemed likely to be a good fit for off-site backups of our OS X server machine. However, despite having seemingly gotten it install