From 9d852bff729d2dfd0e01aa39a1b0c3abe541493b Mon Sep 17 00:00:00 2001 From: spwhitton Date: Fri, 5 Aug 2016 16:20:12 +0000 Subject: ask for sbuild feedback --- doc/todo/updates_for_sbuild_0.70.0-1.mdwn | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/todo/updates_for_sbuild_0.70.0-1.mdwn (limited to 'doc/todo/updates_for_sbuild_0.70.0-1.mdwn') diff --git a/doc/todo/updates_for_sbuild_0.70.0-1.mdwn b/doc/todo/updates_for_sbuild_0.70.0-1.mdwn new file mode 100644 index 00000000..0c668340 --- /dev/null +++ b/doc/todo/updates_for_sbuild_0.70.0-1.mdwn @@ -0,0 +1,19 @@ +sbuild 0.70.0-1 no longer installs gnupg into chroots on each build. That means that if you have an sbuild apt keypair generated, the build will fail unless you enter the source chroot and install gnupg. + +It turns out that the apt keypair is only needed if you're trying to build for wheezy or older. Otherwise, you can just use sbuild without such a keypair. So we have two options to fix Sbuild.hs: + +1. Install gnupg into chroots. + + - This is easy for newly created chroots. + + - The code to update existing chroots will be unpleasant, because we don't want to run propellor inside the sbuild chroot so that it remains standardised (that's why we create it with sbuild-createchroot). + +2. Drop support for building for wheezy and newer, replacing the `keypairGenerated` and `keypairInsecurelyGenerated` properties with a property that ensures that the keypair directory does not exist. + + - Wheezy is very old. + + - This will simplify and speed up chroot creation and builds. + +I'd like feedback on these two options before preparing a patch for one of them. + +--spwhitton -- cgit v1.2.3