l" <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" <
- 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
d-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.go
i...@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: &q
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...@phi
"Phil Holmes" 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
- Original Message -
From: "Trevor Daniels" <t.dani...@treda.co.uk>
To: "Paul Morris" <p...@paulwmorris.com>; "Phil Holmes"
<m...@philholmes.net>
Cc: "lilypond-devel" <lilypond-devel@gnu.org>
Sent: Sunday, October 25, 2015
2015-11-01 19:06 GMT+01:00 David Kastrup :
> "Phil Holmes" 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
.com>
> To: "James" <p...@gnu.org>
> Cc: "Phil Holmes" <m...@philholmes.net>; "Trevor Daniels"
> <t.dani...@treda.co.uk>; "lilypond-devel" <lilypond-devel@gnu.org>
> Sent: Monday, October 26, 2015 6:15 PM
> Subject: Re: All
ot; <m...@philholmes.net>; "Trevor Daniels"
<t.dani...@treda.co.uk>; "lilypond-devel" <lilypond-devel@gnu.org>
Sent: Monday, October 26, 2015 6:15 PM
Subject: Re: Allure and git-cl troubleshooting
Thanks Trevor, Phil, and James. I believe I have everything con
- Original Message -
From: "Trevor Daniels" <t.dani...@treda.co.uk>
To: "Paul Morris" <p...@paulwmorris.com>; "Phil Holmes"
<m...@philholmes.net>
Cc: "lilypond-devel" <lilypond-devel@gnu.org>
Sent: Sunday, October 25, 2015
l" <lilypond-devel@gnu.org>
> Sent: Sunday, October 25, 2015 9:48 PM
> Subject: Re: Allure and git-cl troubleshooting
>
>
>>
>> Paul Morris wrote Sunday, October 25, 2015 9:33 PM
>>
>>
>>> I gave git-cl another try and got the same error from
Thanks Trevor, Phil, and James. I believe I have everything configured
correctly. (I removed my bearer token below, but I just double checked and
it’s correct.)
[lilypond-git (whiteout-style)]$ git cl config
Rietveld server (host[:port]) [codereview.appspot.com]:
Allura server
> On Oct 25, 2015, at 5:14 PM, Trevor Daniels wrote:
>
> Thanks Paul - should be good to go now.
Thanks, good to be on board.
I gave git-cl another try and got the same error from my previous message,
ending in:
File "/usr/lib/python2.7/urllib2.py", line 558, in
Paul Morris wrote Sunday, October 25, 2015 9:33 PM
> I gave git-cl another try and got the same error from my previous message,
> ending in:
>
> File "/usr/lib/python2.7/urllib2.py", line 558, in http_error_default
> raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
>
Il giorno dom 25 ott 2015 alle 20:48, Paul Morris
ha scritto:
urllib2.URLError: certificate verify failed (_ssl.c:581)>
Installing the package ca-certificates should fix it (I added it to
LilyDev after generating the ISO you are using...).
> On Oct 25, 2015, at 4:13 PM, Federico Bruni wrote:
>
> Il giorno dom 25 ott 2015 alle 20:48, Paul Morris ha
> scritto:
>> urllib2.URLError: > certificate verify failed (_ssl.c:581)>
>
> Installing the package ca-certificates should fix it (I added
Paul Morris wrote Sunday, October 25, 2015 7:48 PM
> Below is an error I got trying to upload with git-cl, the new Allura version
> that’s in LilyDev4. I followed James and Phil’s recent email exchange about
> how to do config with Allura server url, source forge account, bearer token,
>
> On Oct 25, 2015, at 4:32 PM, Trevor Daniels wrote:
>
> Maybe not the cause of this particular problem, but only authenticated
> developers are permitted to edit tickets, which is what git-cl needs to do.
> Anyone submitting a patch is de facto a developer, so all you
Paul, you wrote Sunday, October 25, 2015 8:45 PM
>> On Oct 25, 2015, at 4:32 PM, Trevor Daniels wrote:
>>
>> Maybe not the cause of this particular problem, but only authenticated
>> developers are permitted to edit tickets, which is what git-cl needs to do.
>> Anyone
Greetings devs,
Below is an error I got trying to upload with git-cl, the new Allura version
that’s in LilyDev4. I followed James and Phil’s recent email exchange about
how to do config with Allura server url, source forge account, bearer token,
etc.
Any ideas on why it’s not working? Do
21 matches
Mail list logo