James Lowe wrote Thursday, May 28, 2015 7:04 AM > > On 27/05/15 21:17, David Kastrup wrote: >> James <p...@gnu.org> writes: >> >>> On 27/05/15 09:43, David Kastrup wrote: >>>> David Kastrup <d...@gnu.org> writes: >>>> >>>>> I tried uploading about 4 hours ago but I don't get anything except >>>>> >>>>> result = func(*args) >>>>> File "/usr/lib/python2.7/urllib2.py", line 558, in http_error_default >>>>> raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) >>>>> urllib2.HTTPError: HTTP Error 404: Not Found >>>>> >> Asked Han-Wen. What's going on is that password authentication is no >> more with Google. >> >> <URL:http://googledevelopers.blogspot.ch/2015/02/reminder-clientlogin-shutdown-scheduled.html> >> >> So what I did was pressed "Create Issue" on codereview.appspot.com which >> tells you to use update.py and provides a download for it. So I >> downloaded it, overwrote the version in the git-cl directory (which does >> not know about oauth2) with it, edited the --oauth2 option to default to >> True (since I did not figure out how upload.py is getting called by >> git-cl). >> >> So now git-cl -n works again. But git cl does not just need to >> communicate with Rietveld. Everything else (which basically means >> Google Code) doesn't, consequently. So neither does Patchy. >> >> Got a headache now. But at least I updated issue 4422 with a Rietveld >> review. Even though Patchy can't comment on it. > > https://developers.google.com/gdata/docs/auth/overview?csw=1 > > That explains why test-patchy (and probably accept/reject-patchy) don't > work either.
Given this problem I thought it prudent to see if I could still import the Issues DB from GoogleCode to Allura in SourceForge. I started the import at 12 noon today (28 May) and after a disconcertingly long pause before anything happened it now seems to be proceeding normally. Trevor _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
