thanks for the report, I need to work on a feature to get circleci cross-compiling all pushes (branches and forks)

@srfraser do you mean that the git pull failure is "expected behavior"? ie, when git pull fails, package.sh builds from the intended branch?

PS: circleci should now be making debs and rpms, see the "artifacts" tab on any successful build

Yes, when the git pull fails, it builds from the intended branch. When it succeeds (because the branch config is there), it builds from master.

It would still be useful to test the building of debs and rpms before it reaches circleci

@srfraser, it appears that go get ./... switches to the master branch IFF there is an upstream branch set.

I don't know why it does that, but the only solution I could come up with is to unset the remote branch before running that command, and log a warning that it happened. Let me know what you think (see referenced commit)

There could be an optional argument to package.sh, specifying the branch. If not given, set to master, then after go get ./... then git checkout branchname. It might be more work than desired for this use case, though.

I agree but I think it's a bit too much for this use-case, as it stands the script doesn't really have any arg parsing, I would rather keep it simple, especially since you can now get the .deb and .rpm files via circle