Re: Error in git-cl creating a new issue

[Thomas Morley]

2016-01-06 4:07 GMT+01:00 John Gourlay :
> I just submitted a small change to the Contributors Guide using git-cl. The 
> patch got into codereview.appspot.com, but not into 
> sourceforge.net/p/testlilyissues/issues/. I let git-cl create a new issue for 
> the patch, but it produced a bunch of error messages. Does anyone have an 
> idea about why?

No clue, sorry.
Phil, who did recent changes, is in holidays for three weeks, iirc

> How do I proceed now?

I'd enter the tracker-issue manually.
With a link to Rietveld
https://codereview.appspot.com/282960043/

> The error messages were:
[...]
>
> John Gourlay


Btw, I use the command
git cl upload origin/master
i.e. without the dash.

My git-cl is at:
~/git-cl (master)$ git log
commit 5a8f66d7568a8cdc3de246f26cb538ac08315791
Author: Phil Holmes 
Date:   Tue Dec 29 14:36:38 2015 +

More information if new issue fails



Cheers,
  Harm

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

Re: Error in git-cl creating a new issue

[Simon Albrecht]

On 06.01.2016 13:26, Trevor Daniels wrote:

John Gourlay, you wrote Wednesday, January 06, 2016 3:07 AM



I just submitted a small change to the Contributors Guide using git-cl. The 
patch got into codereview.appspot.com, but not into 
sourceforge.net/p/testlilyissues/issues/. I let git-cl create a new issue for 
the patch, but it produced a bunch of error messages. Does anyone have an idea 
about why? How do I proceed now? The error messages were:

It was because you had Member rather than Developer status at SourceForge.  
I've upgraded you now.  Please try again.


Ah, interesting. Would that be the same for me? I had the same problem.

Yours, Simon

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

Re: Error in git-cl creating a new issue

[Simon Albrecht]

On 06.01.2016 12:48, Thomas Morley wrote:

2016-01-06 4:07 GMT+01:00 John Gourlay :

I just submitted a small change to the Contributors Guide using git-cl. The 
patch got into codereview.appspot.com, but not into 
sourceforge.net/p/testlilyissues/issues/. I let git-cl create a new issue for 
the patch, but it produced a bunch of error messages. Does anyone have an idea 
about why?

No clue, sorry.
Phil, who did recent changes, is in holidays for three weeks, iirc


How do I proceed now?

I'd enter the tracker-issue manually.
With a link to Rietveld
https://codereview.appspot.com/282960043/


The error messages were:

[...]

John Gourlay


Btw, I use the command
git cl upload origin/master
i.e. without the dash.


Should be completely synonymous, shouldn’t it?



My git-cl is at:
~/git-cl (master)$ git log
commit 5a8f66d7568a8cdc3de246f26cb538ac08315791
Author: Phil Holmes 
Date:   Tue Dec 29 14:36:38 2015 +

 More information if new issue fails


That introduced the ‘Failed URL was…’ and ‘Failed data was…’ messages 
instead of something more cryptic.


Yours, Simon

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

Re: Error in git-cl creating a new issue

[Trevor Daniels]

John Gourlay, you wrote Wednesday, January 06, 2016 3:07 AM


>I just submitted a small change to the Contributors Guide using git-cl. The 
>patch got into codereview.appspot.com, but not into 
>sourceforge.net/p/testlilyissues/issues/. I let git-cl create a new issue for 
>the patch, but it produced a bunch of error messages. Does anyone have an idea 
>about why? How do I proceed now? The error messages were:

It was because you had Member rather than Developer status at SourceForge.  
I've upgraded you now.  Please try again.

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

Re: Error in git-cl creating a new issue

[Trevor Daniels]

Simon Albrecht, you wrote Wednesday, January 06, 2016 1:14 PM

> On 06.01.2016 13:26, Trevor Daniels wrote:
>> John Gourlay, you wrote Wednesday, January 06, 2016 3:07 AM
>>
>>
>>> I just submitted a small change to the Contributors Guide using git-cl. The 
>>> patch got into codereview.appspot.com, but not into 
>>> sourceforge.net/p/testlilyissues/issues/. I let git-cl create a new issue 
>>> for the patch, but it produced a bunch of error messages. Does anyone have 
>>> an idea about why? How do I proceed now? The error messages were:
>> It was because you had Member rather than Developer status at SourceForge.  
>> I've upgraded you now.  Please try again.
> 
> Ah, interesting. Would that be the same for me? I had the same problem.

No, you've always had Dev status.  In fact you were the second one after James 
to be added.  Must be something else in your case.  Has git-cl never worked for 
you?

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

Re: Error in git-cl creating a new issue

[Simon Albrecht]

On 06.01.2016 15:10, Trevor Daniels wrote:

Simon Albrecht, you wrote Wednesday, January 06, 2016 1:14 PM


On 06.01.2016 13:26, Trevor Daniels wrote:

John Gourlay, you wrote Wednesday, January 06, 2016 3:07 AM



I just submitted a small change to the Contributors Guide using git-cl. The 
patch got into codereview.appspot.com, but not into 
sourceforge.net/p/testlilyissues/issues/. I let git-cl create a new issue for 
the patch, but it produced a bunch of error messages. Does anyone have an idea 
about why? How do I proceed now? The error messages were:

It was because you had Member rather than Developer status at SourceForge.  
I've upgraded you now.  Please try again.

Ah, interesting. Would that be the same for me? I had the same problem.

No, you've always had Dev status.  In fact you were the second one after James 
to be added.  Must be something else in your case.  Has git-cl never worked for 
you?


The rietveld part is fine. Only the Allura part reliably fails, with the 
same kind of messages that John reported.

I’ve just been creating issues manually.

Yours, Simon

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

Re: Error in git-cl creating a new issue

[John Gourlay]

I tried to add an issue to the SourceForge issues list by hand, and I got an 
error email message. Could this be the git-cl problem? The email message says:

Your mail to 'Testlilyissues-auto' with the subject

   [testlilyissues:issues] #4724 Fix typographical errors in
Contributor's Guide related to git-cl.

Is being held until the list moderator can review it for approval.

The reason it is being held:

   Post by non-member to a members-only list



> On Jan 6, 2016, at 11:24 AM, Trevor Daniels  wrote:
> 
> 
> Simon, you wrote Wednesday, January 06, 2016 4:05 PM
> 
>> The rietveld part is fine. Only the Allura part reliably fails, with the 
>> same kind of messages that John reported.
>> I’ve just been creating issues manually.
> 
> Well, a 403 HTTP error means the server received and understood
> the request but decided the request was forbidden.
> 
> Assuming you have a valid bearer token, see
> 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.
> 
> If neither of these are the reason we'll have to wait until 
> Phil can take a look.
> 
> Trevor
> 
> 


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

Re: Error in git-cl creating a new issue

[Trevor Daniels]

Simon, you wrote Wednesday, January 06, 2016 4:05 PM

> The rietveld part is fine. Only the Allura part reliably fails, with the 
> same kind of messages that John reported.
> I’ve just been creating issues manually.

Well, a 403 HTTP error means the server received and understood
the request but decided the request was forbidden.

Assuming you have a valid bearer token, see
 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.

If neither of these are the reason we'll have to wait until 
Phil can take a look.

Trevor


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

Re: Error in git-cl creating a new issue

[John Gourlay]

This was the first time I tried to use git-cl. I made another small 
typographical fix to the Contributor’s Guide and submitted the new patch. I got 
the same error. I have the Allura server url set correctly, and I have a bearer 
token that I obtained following the instructions in the Contributor’s Guide. I 
don’t know how to verify that it is actually correct, however.

> On Jan 6, 2016, at 11:24 AM, Trevor Daniels  wrote:
> 
> 
> Simon, you wrote Wednesday, January 06, 2016 4:05 PM
> 
>> The rietveld part is fine. Only the Allura part reliably fails, with the 
>> same kind of messages that John reported.
>> I’ve just been creating issues manually.
> 
> Well, a 403 HTTP error means the server received and understood
> the request but decided the request was forbidden.
> 
> Assuming you have a valid bearer token, see
> 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.
> 
> If neither of these are the reason we'll have to wait until 
> Phil can take a look.
> 
> Trevor
> 
> 


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

Error in git-cl creating a new issue

[John Gourlay]

I just submitted a small change to the Contributors Guide using git-cl. The 
patch got into codereview.appspot.com, but not into 
sourceforge.net/p/testlilyissues/issues/. I let git-cl create a new issue for 
the patch, but it produced a bunch of error messages. Does anyone have an idea 
about why? How do I proceed now? The error messages were:

Please enter a valid tracker issue number
(or enter nothing to create a new issue): 
Error code 403
Failed URL was https://sourceforge.net/rest/p/testlilyissues/issues//new
Failed data was 
ticket_form.summary=Change+several+instances+of+%22git+cl%22+in+the+Contributors+Guide+to+%22git-cl%22._form.custom_fields._patch=new_form.custom_fields._type=Enhancement_form.description=Change+several+instances+of+%22git+cl%22+in+the+Contributors+Guide+to+%22git-cl%22.%0A%0Ahttp%3A%2F%2Fcodereview.appspot.com%2F282960043_token=51956463ff919409e05_form.status=Started

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