lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: git-cl upload mimetypes fixed (issue 1491)


From: Julien Rioux
Subject: Re: git-cl upload mimetypes fixed (issue 1491)
Date: Sun, 02 Oct 2011 02:10:47 +0200
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1

On 30/09/2011 1:59 PM, Graham Percival wrote:
Following Nicholas' suggestion from last February, I've fixed the
git-cl upload:
https://github.com/gperciva/git-cl/commit/86d891d0817b0d4946fd22bd03554ea2685337b9

I suggest that everybody using git-cl upgrade to this.

Also note that I've added a
   -s --no_code_issue
option to skip uploading to code.google.com, in case you wanted to
use git-cl for projects other than lilypond.  :)

Cheers,
- Graham

Thanks, I got it to work a bit further: It uploaded to Rietveld, generated some comment on the googlepage, but errored in the end. See traceback below.

Cheers,
Julien

This has been identified with code.google.com issue 1852.
Is this correct? [y/n (y)]y
WARNING: could not change issue labels;
please email lilypond-devel with the issue
Traceback (most recent call last):
  File "../git-cl/git-cl", line 885, in <module>
    sys.exit(main(sys.argv))
  File "../git-cl/git-cl", line 879, in main
    return func(argv[2:])
  File "../git-cl/git-cl", line 609, in CmdUpload
    projecthosting_upload.upload(issue, patchset, subject, desc)
File "/home/jrioux/git/git-cl/projecthosting_upload.py", line 163, in upload
    status = patchy.upload(issue, patchset, subject, description)
File "/home/jrioux/git/git-cl/projecthosting_upload.py", line 144, in upload
    issue, problem = self.update_issue(issue_id, description)
File "/home/jrioux/git/git-cl/projecthosting_upload.py", line 97, in update_issue
    self.generate_devel_error(issue)
File "/home/jrioux/git/git-cl/projecthosting_upload.py", line 79, in generate_devel_error
    print "number: %i" % issue_id
TypeError: %d format: a number is required, not CommentEntry





reply via email to

[Prev in Thread] Current Thread [Next in Thread]