Re: [Duplicity-talk] Deprecation of pydrivebackend

[Chris McGinley]

I was able to make the move over to gdrive after sending over my response. The DriveID, MyDriveFolderID, and the destination URL were not entirely obvious to me from the man page notes; however, with some trial and error, I was able to get it all working.

-Chris

On Tuesday, June 20, 2023 at 06:41:00 AM EDT, edgar.soldin--- via Duplicity-talk <duplicity-talk@nongnu.org> wrote:

hey WIlliam,

how about following the instructions in the man page? :)
  https://duplicity.us/stable/duplicity.1.html#a-note-on-gdrive-backend

good luck ..ede/duply.net

On 19.06.2023 18:53, William via Duplicity-talk wrote:
> I have been using pydrive for 6+ years, as documented in the V8 manual page (https://duplicity.nongnu.org/vers8/duplicity.1.html).
>
> No mention there that pydrive is not to be used.
>
> Is there a cookbook instructions on how to convert the pydrive commands/setup to gdrive.
>
> I use DUPLY to drive the backups, so the necessary EXPORT and file specs are in the DUPLY conf file.
>
>
> On 6/19/23 11:59, Kenneth Loafman via Duplicity-talk wrote:
>> Hi all,
>>
>> Does anyone use the pydrive backend anymore?  This would be a URL schema of "pydrive://", "pydrive+gdocs://" or "gdocs://"
>>
>> It was replaced with the gdrive backend a couple of years ago.  Before we deprecate it I was just trying to find out if there was anyone still using it.  And how?
>>
>> ...Thanks,
>> ...Ken
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> Duplicity-talk@nongnu.org
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>

_______________________________________________
Duplicity-talk mailing list
Duplicity-talk@nongnu.org
https://lists.nongnu.org/mailman/listinfo/duplicity-talk