My apologies. All is working, now. I had forgotten to uncomment the GOOGLE_DRIVE_SETTINGS variable. Awesome. Thank you! -- Forwarded Message -- Subject: Re: [Duplicity-talk] pydrive and google dr
Great instructions, thanks. During my first duplicity run, I get the error: Import of duplicity.backends.pydrive2backend Failed: expected an indented block (pydrive2backend.py, line 60) This is what
I've made a go at the ID cache approach I suggested below. I'm actually not sure if it's needed, since I can't find any docs that indicate what consistency guarantees are in Drive (as opposed to Clou
it's in the development branch http://bazaar.launchpad.net/~duplicity-team/duplicity/0.7-series/files but not released yet. maybe somebody else can give you a hint on how to install a current snapsho
Thanks, that's an interesting link. It's describing Cloud rather than Drive, but it wouldn't surprise me if Drive is similar i.e. an object store with a filesystem duct-taped on. That makes me think
Thanks, that's an interesting link. It's describing Cloud rather than Drive, but it wouldn't surprise me if Drive is similar i.e. an object store with a filesystem duct-taped on. That makes me think
In the latest version of the pydrive backend, you can do this by setting GOOGLE_DRIVE_SETTINGS rather than GOOGLE_DRIVE_ACCOUNT_KEY (see the man page for details). Rupert
OK, log.Warn should be changed to log.FatalError, I guess. To make _delete remove all files, the simplest way might be def _delete(self, filename): flist = self.FilesList(filename) for f in flist: f.
Hello, I have successfully connect and upload content with the pydrive backend but i failed to see the content on my google drive. I know it is not directly related to duplicity but if someone know h
looks good. not sure about (2) which might probably work, but probably is error, so i'd rather had a fatal error thrown and the user deal with it than silently use the first listed. who guarantees th
I think what is happening is that during a backup, duplicity checks the size of a file on Google Drive after each upload, and sometimes this call returns -1. (The original upload often appears to hav
On 10 June 2015 at 02:04, <address@hidden> wrote: i couldn't find a place where the success of the upload is verified via a size retrieved afterwards. it merely looks like google drive stores files v
i couldn't find a place where the success of the upload is verified via a size retrieved afterwards. it merely looks like google drive stores files via a unique id and folder and file name are just m
I also get duplicate files (same filename, same parent folder) in Google Drive when using duplicity and have to remove them manually before retrying. On large backups (thousands of volumes) this happ
<snip> Yes, I've double-checked it in the GUI. I used a quick PyDrive script to get a list of all files in the drive which is attached, but it doesn't distinguish what directory everything is in (Goo
Hi (apologies if this shows up twice - my first attempt was without subscribing to the list, and since it didn't show up in the list archives I'm assuming it went to the bit-bucket) I've somehow mana