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