Add a gnupg keyring containing just the public part of the keypair used
to sign release tags.
Also change the githelper script to use the keyring in the git repo
instead of the one in the caller's home directory.
Signed-off-by: Sebastian Kuzminsky <seb@highlab.com>
My previous panicked change broke the git helper script, by inadvertently
moving some error messages from stderr to stdout.
The problem *doesn't* manifest if the user who runs the script has Jeff
Epler's or Chris Radek's pubkeys in their key ring, like I do.
The problem *does* manifest if neither of those keys are in the user's
key ring, like on one of the buildbot machines.
This commit puts the error messages back where they belong.
If i tell you what branch i'm on, you tell me which debian archive
component to put the packages in. This feature is useful for automation
that builds emc2 and makes debian archives (buildbot, i'm looking at you).
We used to always use the branch name as the component name, for example
the v2.4_branch debs went into the v2.4_branch-{sim,rt} components.
This falls short if you want to do test builds of throw-away branches,
because the binary deb builders don't know the name of your branch, so
they don't know where to find the source debs. This commit puts all
unknown branches into a new component named "scratch", so the binary
deb builders' sources.list doesn't have to know all the branch names.
This commit does these things:
* Add a small shell library called githelper.sh, which reads a bunch
of info from git and makes it available as environment variables
in the caller.
* Add a script called version-is-release, which checks to see if
the current version (HEAD) has a signed release tag pointing to it.
* Update update-dch-from-git and get-version-from-git to use the
new githelper library, for consistency.
