Re: Allure and git-cl troubleshooting

[Phil Holmes]

- Original Message - 
From: "James Lowe" <p...@gnu.org>

To: "Phil Holmes" <m...@philholmes.net>; "David Kastrup" <d...@gnu.org>
Cc: "lilypond-devel" <lilypond-devel@gnu.org>; "Trevor Daniels" 
<t.dani...@treda.co.uk>

Sent: Monday, November 02, 2015 6:11 PM
Subject: Re: Allure and git-cl troubleshooting



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.


Adding a print statement to print out upload_args gives this:

['--assume_yes', '--server', 'codereview.appspot.com', '--cc', 
'lilypond-devel@gnu.org', '--issue', '269820043', '--title', 'testy', 
'--message', 'testy', '--oauth2']


I used the word 'testy' for the description of the patch set...

Think it's fairly simple to parse that into a command line.

--
Phil Holmes 



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[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 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.


--
Phil Holmes 



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Phil Holmes]

- 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 



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[James Lowe]

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

Re: Allure and git-cl troubleshooting

[Thomas Morley]

2015-11-02 16:40 GMT+01:00 Phil Holmes <m...@philholmes.net>:
> - 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.
>
>
> --
> Phil Holmes



Could upload now.

Terminal output is different than before:
~/lilypond-git (dev/quarter-tone-tab)$ git cl upload origin/master
 Documentation/changes.tely   | 18 
 Documentation/notation/fretted-strings.itely | 38 +
 input/regression/tablature-micro-tone.ly | 42 
 ly/engraver-init.ly  |  3 +-
 scm/translation-functions.scm| 36 +++-
 5 files changed, 129 insertions(+), 8 deletions(-)
Upload server: codereview.appspot.com (change with -s/--server)
Your browser has been opened to visit:

https://codereview.appspot.com/get-access-token?port=8001

If your browser is on a different machine then exit and re-run
upload.py with the command-line parameter

  --no_oauth2_webbrowser


(process:3169): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed
Issue created. URL: http://codereview.appspot.com/272320043
Uploading base file for Documentation/changes.tely
Uploading base file for scm/translation-functions.scm
Uploading base file for input/regression/tablature-micro-tone.ly
Uploading base file for Documentation/notation/fretted-strings.itely
Uploading base file for ly/engraver-init.ly
This has been identified with issue 4643.
Is this correct? [y/n (y)]y
Ticket 
https://sourceforge.net/rest/p/testlilyissues/issues/_discuss/thread/994f86c3/7eff/
updated
Tracker issue done: 4643

Pretty much as expected, I'd think.

This one doesn't belong to git-cl:
(process:3169): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed
I always get this, whenever starting firefox from terminal.

The issue changed to "patch new"
The owner wasn't updated. Though, I don't know if it should ...


Thanks a lot,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[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
> 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

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Phil Holmes]

- 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 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 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)
urllib2.HTTPError: HTTP Error 404: Not Found


Hhm, assuming you've got a bearer token from
https://sourceforge.net/auth/oauth/,
and have set up the full url to the correct page:
https://sourceforge.net/p/testlilyissues/issues/
I don't know what else might be wrong.

We'll have to let Phil have a look.

Trevor



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?


--
Phil Holmes 



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Thomas Morley]

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
>> 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



After having pushed two patches today I wanted to upload a new one for
issue 4643

I get an error similiar to the one Paul initially reported:

~/lilypond-git (dev/quarter-tone-tab)$ git cl upload origin/master
 Documentation/changes.tely   | 18 
 Documentation/notation/fretted-strings.itely | 38 +
 input/regression/tablature-micro-tone.ly | 42 
 ly/engraver-init.ly  |  3 +-
 scm/translation-functions.scm| 36 +++-
 5 files changed, 129 insertions(+), 8 deletions(-)
Upload server: codereview.appspot.com (change with -s/--server)
Loaded authentication cookies from /home/hermann/.codereview_upload_cookies
Email (login for uploading to codereview.appspot.com)
[thomasmorley65]: thomasmorley65
Password for thomasmorley65:
Traceback (most recent call last):
  File "/home/hermann/git-cl/git-cl", line 629, in 
sys.exit(main(sys.argv))
  File "/home/hermann/git-cl/git-cl", line 623, in main
return func(argv[2:])
  File "/home/hermann/git-cl/git-cl", line 334, in CmdUpload
issue, patchset = upload.RealMain(['upload'] + upload_args + args)
  File "/home/hermann/git-cl/upload.py", line 2342, in RealMain
response_body = rpc_server.Send("/upload", body, content_type=ctype)
  File "/home/hermann/git-cl/upload.py", line 409, in Send
self._Authenticate()
  File "/home/hermann/git-cl/upload.py", line 428, in _Authenticate
super(HttpRpcServer, self)._Authenticate()
  File "/home/hermann/git-cl/upload.py", line 318, in _Authenticate
auth_token = self._GetAuthToken(credentials[0], credentials[1])
  File "/home/hermann/git-cl/upload.py", line 262, in _GetAuthToken
response = self.opener.open(req)
  File "/usr/lib/python2.7/urllib2.py", line 437, in open
response = meth(req, response)
  File "/usr/lib/python2.7/urllib2.py", line 550, in http_response
'http', request, response, code, msg, hdrs)
  File "/usr/lib/python2.7/urllib2.py", line 475, in error
return self._call_chain(*args)
  File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
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

No idea why this happens, I didn't change anything in my git-settings


Cheers,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Paul Morris]

Hi Trevor,

You’re right.  I also just looked closer at the traceback and at the function 
_GetAuthToken in git-cl/upoad.py where things go wrong (line 262).  The doc 
string says that function raises a ClientLoginError for authentication 
problems, and an HTTPError for "some other form of HTTP error”.  And the 
traceback I got ends with an HTTPError, namely 404 not found.  So it sounds 
like it’s may not be a problem with the authentication with google per se, but 
with connecting with google in the first place.

-Paul

> On Oct 26, 2015, at 3:29 PM, Trevor Daniels <t.dani...@treda.co.uk> wrote:
> 
> Hi Paul
> 
> Looking at the error again it seems to be a problem with authenticating at 
> GoogleCode rather than Allura at SourceForge.
> 
> Trevor
> 
> - Original Message - 
> From: "Paul Morris" <p...@paulwmorris.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: Allure and git-cl troubleshooting
> 
> 
> 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 [https://sourceforge.net/p/testlilyissues/issues/]: 
> Allura bearer token (see https://sourceforge.net/auth/oauth/) 
> [***REMOVED***]: 
> CC list ("x" to clear) [lilypond-devel@gnu.org]: 
> 
> -Paul


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Trevor Daniels]

Hi Paul

Looking at the error again it seems to be a problem with authenticating at 
GoogleCode rather than Allura at SourceForge.

Trevor

- Original Message - 
From: "Paul Morris" <p...@paulwmorris.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: Allure and git-cl troubleshooting


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 [https://sourceforge.net/p/testlilyissues/issues/]: 
Allura bearer token (see https://sourceforge.net/auth/oauth/) [***REMOVED***]: 
CC list ("x" to clear) [lilypond-devel@gnu.org]: 

-Paul
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Phil Holmes]

- 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 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 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)
urllib2.HTTPError: HTTP Error 404: Not Found


Hhm, assuming you've got a bearer token from
https://sourceforge.net/auth/oauth/,
and have set up the full url to the correct page:
https://sourceforge.net/p/testlilyissues/issues/
I don't know what else might be wrong.

We'll have to let Phil have a look.

Trevor



I'd bet it's getting the URL to the correct page right: the one you cite 
above.  The error could be more enlightening, though.  I'd suggest Paul 
checks his URL, and when I have time I'll look at sorting an error trap.


--
Phil Holmes 



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[James]

Paul

On 26/10/15 15:25, Phil Holmes wrote:
> - 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 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 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)
>>> urllib2.HTTPError: HTTP Error 404: Not Found
>>
>> Hhm, assuming you've got a bearer token from
>> https://sourceforge.net/auth/oauth/,
>> and have set up the full url to the correct page:
>> https://sourceforge.net/p/testlilyissues/issues/
>> I don't know what else might be wrong.
>>
>> We'll have to let Phil have a look.
>>
>> Trevor
>
>
> I'd bet it's getting the URL to the correct page right: the one you
> cite above.  The error could be more enlightening, though.  I'd
> suggest Paul checks his URL, and when I have time I'll look at sorting
> an error trap.


You can re-run git-cl config again in the terminal and check the URL.

James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Paul Morris]

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 [https://sourceforge.net/p/testlilyissues/issues/]: 
Allura bearer token (see https://sourceforge.net/auth/oauth/) [***REMOVED***]: 
CC list ("x" to clear) [lilypond-devel@gnu.org]: 

-Paul


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Paul Morris]

> 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 http_error_default
  raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 404: Not Found

-Paul
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Trevor Daniels]

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)
> urllib2.HTTPError: HTTP Error 404: Not Found

Hhm, assuming you've got a bearer token from
https://sourceforge.net/auth/oauth/, 
and have set up the full url to the correct page:
https://sourceforge.net/p/testlilyissues/issues/
I don't know what else might be wrong.

We'll have to let Phil have a look.

Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Federico Bruni]

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...).





___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Paul Morris]

> 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 it to LilyDev 
> after generating the ISO you are using...).

Thanks Federico.  I did that, tried it again, and got a different error:

Upload server: codereview.appspot.com (change with -s/--server)
Email (login for uploading to codereview.appspot.com) [paulwmor...@gmail.com]:
paulwmor...@gmail.com
Password for paulwmor...@gmail.com:
Traceback (most recent call last):
 File "/home/paul/git-cl/git-cl", line 629, in 
   sys.exit(main(sys.argv))
 File "/home/paul/git-cl/git-cl", line 623, in main
   return func(argv[2:])
 File "/home/paul/git-cl/git-cl", line 334, in CmdUpload
   issue, patchset = upload.RealMain(['upload'] + upload_args + args)
 File "/home/paul/git-cl/upload.py", line 2342, in RealMain
   response_body = rpc_server.Send("/upload", body, content_type=ctype)
 File "/home/paul/git-cl/upload.py", line 383, in Send
   self._Authenticate()
 File "/home/paul/git-cl/upload.py", line 428, in _Authenticate
   super(HttpRpcServer, self)._Authenticate()
 File "/home/paul/git-cl/upload.py", line 318, in _Authenticate
   auth_token = self._GetAuthToken(credentials[0], credentials[1])
 File "/home/paul/git-cl/upload.py", line 262, in _GetAuthToken
   response = self.opener.open(req)
 File "/usr/lib/python2.7/urllib2.py", line 437, in open
   response = meth(req, response)
 File "/usr/lib/python2.7/urllib2.py", line 550, in http_response
   'http', request, response, code, msg, hdrs)
 File "/usr/lib/python2.7/urllib2.py", line 475, in error
   return self._call_chain(*args)
 File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
   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




___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Trevor Daniels]

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, 
> etc.  
> 
> Any ideas on why it’s not working?  Do I need to be an authorized user on the 
> Allura tracker, perhaps?

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 need to do is 
Join (see the Join button top right on the Issues page) the TestLilyIssues 
project and announce on the devel list what username you have chosen and we'll 
authorise you as a Developer.

Trevor

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Paul Morris]

> 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 need to do is 
> Join (see the Join button top right on the Issues page) the TestLilyIssues 
> project and announce on the devel list what username you have chosen and 
> we'll authorise you as a Developer.

Ok, my username on sourceforge is paulwmorris.

Thanks,
-Paul
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Trevor Daniels]

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 submitting a patch is de facto a developer, so all you need to do is 
>> Join (see the Join button top right on the Issues page) the TestLilyIssues 
>> project and announce on the devel list what username you have chosen and 
>> we'll authorise you as a Developer.
> 
> Ok, my username on sourceforge is paulwmorris.

Thanks Paul - should be good to go now.

Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Allure and git-cl troubleshooting

[Paul Morris]

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 I need to be an authorized user on the 
Allura tracker, perhaps?

-Paul


[lilypond-git (whiteout-style)]$ git cl upload origin/master
 Documentation/changes.tely | 
40 
 Documentation/fr/notation/rhythms.itely|  
2 +-
 Documentation/notation/rhythms.itely   |  
2 +-
 Documentation/snippets/blanking-staff-lines-using-the--whiteout-command.ly |  
8 
 Documentation/snippets/new/using-the-whiteout-property.ly  |  
6 +++---
 Documentation/snippets/using-the-whiteout-property.ly  |  
4 ++--
 input/regression/markup-syntax.ly  |  
3 +--
 input/regression/whiteout-lower-layers.ly  | 
10 +-
 input/regression/whiteout.ly   | 
20 
 lily/grob.cc   | 
16 +++-
 lily/lily-imports.cc   |  
1 -
 python/convertrules.py |  
7 +++
 scm/define-grob-properties.scm | 
18 --
 scm/define-grobs.scm   |  
2 +-
 scm/define-markup-commands.scm | 
42 +-
 scm/stencil.scm| 
24 
 16 files changed, 113 insertions(+), 92 deletions(-)
Upload server: codereview.appspot.com (change with -s/--server)
Email (login for uploading to codereview.appspot.com) [paulwmor...@gmail.com]: 
paulwmor...@gmail.com
Password for paulwmor...@gmail.com: 
Traceback (most recent call last):
  File "/home/paul/git-cl/git-cl", line 629, in 
sys.exit(main(sys.argv))
  File "/home/paul/git-cl/git-cl", line 623, in main
return func(argv[2:])
  File "/home/paul/git-cl/git-cl", line 334, in CmdUpload
issue, patchset = upload.RealMain(['upload'] + upload_args + args)
  File "/home/paul/git-cl/upload.py", line 2342, in RealMain
response_body = rpc_server.Send("/upload", body, content_type=ctype)
  File "/home/paul/git-cl/upload.py", line 383, in Send
self._Authenticate()
  File "/home/paul/git-cl/upload.py", line 428, in _Authenticate
super(HttpRpcServer, self)._Authenticate()
  File "/home/paul/git-cl/upload.py", line 318, in _Authenticate
auth_token = self._GetAuthToken(credentials[0], credentials[1])
  File "/home/paul/git-cl/upload.py", line 262, in _GetAuthToken
response = self.opener.open(req)
  File "/usr/lib/python2.7/urllib2.py", line 431, in open
response = self._open(req, data)
  File "/usr/lib/python2.7/urllib2.py", line 449, in _open
'_open', req)
  File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
  File "/usr/lib/python2.7/urllib2.py", line 1240, in https_open
context=self._context)
  File "/usr/lib/python2.7/urllib2.py", line 1197, in do_open
raise URLError(err)
urllib2.URLError: 


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel