Add missing reprepro dependency
Merge pull request #7 from zeha/patch-1

Add missing reprepro dependency
generate-git-snapshot: do not increase package version if building for UNRELEASED

This brings generate-git-snapshot closer to what generate-svn-snapshot
already provided, jey.

Thanks: Raphael Hertzog <raphael@ouaza.com> for the suggestion
generate-git-snapshot: check out common branches so git-buildpackage can work with them

Try to check out branches upstream, debian and pristine-tar
which are known to be common branches for building git
projects.

If environment variable $branch is set check out this branch,
otherwise fall back to $GIT_COMMIT as we used to do so far.

I'm still not entirely happy with this but I'm not aware of
anything better yet...
use binary-only build if specified arch doesn't match $MAIN_ARCHITECTURE and/or architecture of host

Quoting Brian:

| The other change I made in build-and-provide-package, was to
| automatically do a binary-only build if the arch specified does not
| match the main architecture and/or the architecture of the host:
|
| http://pastebin.com/mhJGHpV5
|
| Otherwise, both my amd64 and i386 configurations build with the
| default "-sa" build option, each generating a changes file that
| references a .dsc file with a different checksum.  I'm thinking the
| best approach long term might be to have the -source job actually
| upload the source package to reprepro leaving
| build-and-provide-package to always just build with -B.  Your
| thoughts? In the meantime, I've just made the change above.
|
| It looks like you were addressing the problem on your end as well with
| (I can see it executed in your dpkg jobs on http://jenkins.grml.org):
|
|       if grep -q '^Architecture: all' "$control_file" ; then
|         if grep -q '^Architecture: any' "$control_file" ; then
|           echo "*** Package provides arch 'all' + 'any', enabling -B
| buildoption for this architecture. ***"
|           # -B -> binary-only build, limited to architecture dependent packages
|           DEBBUILDOPTS="-B"
|
| However, this code won't work as intended if, for instance, a control
| file contains:
|
| Architecture: i386 amd64

Thanks: Brian Thomason <brian.thomason@eucalyptus.com> for the initial patch
Do not hardcode "sid" as default for cowbuilder dist, support setting COWBUILDER_DIST [Closes #8]

On e.g. Ubuntu "sid" isn't supported, so we can't just hardcode it.
Instead support setting COWBUILDER_DIST via /etc/jenkins/debian_glue
and if it's not set then use "$distribution" if it's set, otherwise
default to the currently running distribution and just fallback to
"sid" if none of all of that worked.

Thanks: Daniel Thomas for the detailed bugreport
fabfile: add further jenkins slaves
fabfile: adjust regex to match all jenkins-debian-glue packages
Display jenkins-debian-glue version in script output

This makes debugging easier if all we have are build logs
Make all shell scripts bash ones

To avoid bashisms :)
Bump Standards-Version to 3.9.3
First release 0.1.0

It's time for getting the baby officially out :)
generation-git-snapshot: use git-dch's auto mode as default

Use our "manual" way of identifying latest merge/tag (known
as identify_latest_change in the implementation) only if
invoked with cmdline option "identify", otherwise default
to git-dch's auto mode which does a better job in most situations.

While at it slightly refactor the identify_latest_change code
and also drop the "j" from git rev-list's --tag option.
generate-git-snapshot: do not checkout branch but always $GIT_COMMIT

The checkout of the branch might be behind, so just use the
$GIT_COMMIT we get. This addresses situations like:

| + git checkout master
| Previous HEAD position was 6293f12... Bump version to 1.16.9
| Switched to branch 'master'
| Your branch is behind 'origin/master' by 426 commits, and can be fast-forwarded.
generate-git-snapshot: use plain dch if handling UNRELEASED version

We can't use git-dch's auto mode if we've to deal with
a distribution being set to UNRELEASED because that fails
with:

| + git-dch --auto -S --multimaint-merge --ignore-branch --new-version=1.16.9~1343298526.109
| Changelog last touched at '6293f12440f48c1e245033801f151e4c99114db7'
| Continuing from commit '6293f12440f48c1e245033801f151e4c99114db7'
| No changes detected from 6293f12440f48c1e245033801f151e4c99114db7 to HEAD.
| dch: fatal error at line 984:
| New version specified (1.16.9~1343298526.109) is less than
| the current version number (1.16.9)!  Use -b to force.
|  dch --no-auto-nmu  --distribution=UNRELEASED --newversion=1.16.9~1343298526.109 --multimaint-merge -- "UNRELEASED" returned 25
| Couldn't run ' dch --no-auto-nmu  --distribution=UNRELEASED --newversion=1.16.9~1343298526.109 --multimaint-merge -- "UNRELEASED"'

So instead run dch with custom command line to get a
version number being smaller than the one that will be
released later on.
Release new version 0.1.1
trigger_jenkins: support sending tags to a release dashboard + iterate over all modified projects
Update svn setup instructions.

For svn, the local subdirectory message is worded a bit differently.
Remove duplicate signal from trap call.
Add a workaround for SOURCE_PACKAGE

identify_build_type expects identify_sourcefile to always set
SOURCE_PACKAGE, set it to "*" in this code path. As it is used as a glob
pattern later, this works good enough for now.