Package: sbuild
Version: 0.64.0-1
Tags: patch
Hi maintainer,
Jeffrey Hutzelman mentioned to me that `sbuild-update --keygen` was
creating ASCII-armored archive keys instead of a binary keyring, which
caused the process of signing the archive to fail. After some confusion on
my part because it totally works for me, we found that he had the armor
option set in his ~/.gnupg/gpg.conf, and that sbuild was respecting this
configuration file.
In order to get consistent scripted behavior out of the gpg command, you
need to pass --no-options. See also apt-key.
Very simple patch attached; you can also pull the single commit from the
gpg-no-options branch of https://github.com/geofft/sbuild if that's easier
. Jeff has confirmed that it fixes his problem.
--
Geoffrey Thomas
http://ldpreload.com
geo...@ldpreload.com
From ad6d39482db4655a619eb26bc8c078deee0d3d87 Mon Sep 17 00:00:00 2001
From: Geoffrey Thomas <geo...@ldpreload.com>
Date: Wed, 21 Aug 2013 22:11:49 -0700
Subject: [PATCH] Sbuild::ChrootSetup: Pass --no-options to gpg
---
lib/Sbuild/ChrootSetup.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/Sbuild/ChrootSetup.pm b/lib/Sbuild/ChrootSetup.pm
index ab16e3c..649c5f3 100644
--- a/lib/Sbuild/ChrootSetup.pm
+++ b/lib/Sbuild/ChrootSetup.pm
@@ -261,7 +261,7 @@ EOF
return $?
}
- my @command = ('gpg', '--no-default-keyring', '--batch', '--gen-key',
+ my @command = ('gpg', '--no-options', '--no-default-keyring', '--batch', '--gen-key',
$tmpfilename);
$host->run_command(
{ COMMAND => \@command,
--
1.8.4
