On 02/11/15 15:40, Phil Holmes wrote: > ----- Original Message ----- From: "Phil Holmes" <m...@philholmes.net> > To: "David Kastrup" <d...@gnu.org> > Cc: "lilypond-devel" <lilypond-devel@gnu.org>; "Trevor Daniels" > <t.dani...@treda.co.uk> > Sent: Monday, November 02, 2015 1:41 PM > Subject: Re: Allure and git-cl troubleshooting > > >> ----- Original Message ----- From: "David Kastrup" <d...@gnu.org> >> To: "Phil Holmes" <m...@philholmes.net> >> Cc: "Trevor Daniels" <t.dani...@treda.co.uk>; "Paul Morris" >> <p...@paulwmorris.com>; "lilypond-devel" <lilypond-devel@gnu.org> >> Sent: Sunday, November 01, 2015 6:06 PM >> Subject: Re: Allure and git-cl troubleshooting >> >> >>> "Phil Holmes" <m...@philholmes.net> writes: >>> >>>> Turns out it is nothing to do with Allura: it's the way Rietveld uses >>>> Google for authentication. See >>>> https://developers.google.com/identity/protocols/AuthForInstalledApps. >>>> Further >>>> thanks to Google for this. >>>> >>>> Question is: should I look into how to fix it, or is there a way to >>>> ask the Rietveld team to fix upload.py and we wait for them? >>> >>> I think they fixed it a long time ago but nobody bothered copying it >>> into our git-cl copy yet. >>> >>> -- >>> David Kastrup >> >> >> Don't think it's a case of "nobody bothered", rather "nobody knew". >> I'll have a look see what has been done. >> >> -- >> Phil Holmes > > > I've pushed an updated version to github. Please all - pull this > updated version of git-cl and let me know how you get on.
Thank you Mr Holmes. That looks like it has done the trick. Out of interest do you know what the upload.py 'command' (in terms of it's construction with the different possible switches) is being used? So that if git-cl breaks again I can at least upload patches to rietveld and then manually update Allura. -- James ------- B8F4 5395 CBE2 ED37 7513 B075 FF32 5682 A84B D8BE _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
