maybe a missing patch from after splitting. Ken: what'd you say? three options: 1. readd the original dev's key 2. create an own, one of us controls 3. externalize them as env vars for users to create themselves
i'd prefer 1. ..ede On 14.11.2014 14:16, Michael Terry wrote: > I don't remember intentionally doing that. > > On 14 November 2014 06:37, <[email protected] <mailto:[email protected]>> > wrote: > > see below.. ede > > > -------- Forwarded Message -------- > Subject: Re: [Duplicity-team] [Question #256351]: Error with dropbox > backend after upgrade to 0.7.0 > Date: Mon, 03 Nov 2014 13:21:58 +0100 > From: Edgar Soldin <[email protected] <mailto:[email protected]>> > To: duplicity-team <[email protected] > <mailto:[email protected]>> > > Ken, Mike, > > any reason why the API KEY was removed? looks like it is standard to > deliver them (albeit obfuscated) with a dropbox client. > > ..ede > > On 02.11.2014 18:41, cp wrote: > > Question #256351 on Duplicity changed: > > https://answers.launchpad.net/duplicity/+question/256351 > > > > cp gave more information on the question: > > Ok, I installed 0.6.25 and extracted the app key which really got lost > in 0.7.0. I put it in dpbxbackend.py and compiled it, and now it seems to be > working again. > > FTP error remains. > > > _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
