Talk:Activity Team/Git Tutorial

Discussion about release.py moved from the main page

 * Note that to release a bundle, all you need to do is upload it to activities.sugarlabs.org. No need to post a source tarball anywhere assuming it's in gitorious.  And I'm not sure release.py is well maintained currently.  Wade 13:52, 4 November 2009 (UTC)


 * 4. I added the pootle user as a committer.
 * 5. Where should I put the .xo bundle? And the source tarball?
 * there is a script for generating and posting changes that covers all of these details.

I had a bit of trouble pushing a new change to gitorious today. I had to use the --force flag for some reason. We suspect it may have something to do with the fact that one of the files I pushed is a binary file. Will report back what I find. (Seems to work fine when there are no binary files to add/push.) git push -fv

I have been trying to use release.py with no luck so far either. (It has a dependency on the feedparser python library, which is easy enough to install.) It complained about a mismatched tag, so I used the --version flag to force the same version number as in my activity.info file. Then I got this error:

nothing added to commit but untracked files present (use "git add" to track) Traceback (most recent call last): File "../release.py", line 325, in    main File "../release.py", line 314, in main release.tag File "../release.py", line 170, in tag subprocess.check_call(['git', 'commit', '-a', '-m', '%s' % message]) File "/usr/lib/python2.5/subprocess.py", line 462, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['git', 'commit', '-a', '-m', 'Release 26']' returned non-zero exit status 1

Is this because I did the git commit and git push by hand before running release.py?