Signbots are started as shown below.
- $ ./signbot.sh --key <keyid>
+ $ ./signbot.sh --gpg-key <keyid>
The purpose of signbot is to sign Debian packages, so you need to tell it which key to
-use using the `--key` option. The key must be a key-id from the default GPG key ring.
+use using the `--gpg-key` option. The key must be a key-id from the default GPG key ring.
By default, signbots are load-balanced the same way as the buildbots. If you want to sign
packages going to one repository with a different key than packages going to a different
repository, you will have to start two signbots with differing `--endpoint` and
$ ./distbot.sh --name deb.example.org \
--output /srv/www/deb \
--arch amd64,i386 \
- --gpgkey <keyid> \
+ --gpg-key <keyid> \
--description "My repository"
Like signbot, distbot needs a GPG key id. Unlike the signbot key, which is used to sign
"The codename of the distribution (default: stable)"
opt_add_arg "a" "arch" "rv" "" \
"Comma separated list of supported architectures"
- opt_add_arg "k" "gpgkey" "rv" "" \
+ opt_add_arg "k" "gpg-key" "rv" "" \
"The GPG key used for signing"
opt_add_arg "d" "description" "rv" "" \
"Description of the repository"
publish_to=$(opt_get "publish-to")
name=$(opt_get "name")
arch=$(opt_get "arch")
- gpgkey=$(opt_get "gpgkey")
+ gpgkey=$(opt_get "gpg-key")
desc=$(opt_get "description")
if ! looks_like_a_repository "$path"; then
opt_add_arg "e" "endpoint" "v" "pub/signbot" "The IPC endpoint to listen on"
opt_add_arg "w" "watch" "v" "builds" "The topic to watch for build messages"
opt_add_arg "p" "publish-to" "v" "signs" "The topic to publish signs under"
- opt_add_arg "k" "key" "rv" "" "Fingerprint of the key to sign with"
+ opt_add_arg "k" "gpg-key" "rv" "" "Fingerprint of the key to sign with"
if ! opt_parse "$@"; then
return 1
endpoint=$(opt_get "endpoint")
watch=$(opt_get "watch")
publish_to=$(opt_get "publish-to")
- key=$(opt_get "key")
+ key=$(opt_get "gpg-key")
if ! inst_start dispatch_tasks "$endpoint" "$watch" "$publish_to" "$key"; then
return 1