Hi, On Tue, Aug 16, 2016 at 12:13:58PM +0200, Johannes Schauer wrote: > Hi, > > Quoting Dominic Hargreaves (2016-08-16 12:09:02) > > However, as has been subsequently pointed out, the workaround (removing > > /var/lib/sbuild/apt-keys) doesn't work with a jessie sbuild: > > > > E: Local archive GPG signing key not found > > I: Please generate a key with 'sbuild-update --keygen' > > I: Note that on machines with scarce entropy, you may wish to generate the > > key with this command on another machine and copy the public and private > > keypair to '/var/lib/sbuild/apt-keys/sbuild-key.pub' and > > '/var/lib/sbuild/apt-keys/sbuild-key.sec' > > Failed to generate archive keys. > > > > so it appears that we do need an update for jessie one way or another? > > if you want to build for unstable on Jessie, then just install the sbuild > version from backports. That one is recent enough.
But I (note: personal view!) don't think it would be a good practice to force users to use backports. It is naturally that e.g. buildds are running on stable, with packages from stable and they then build as well for unstable. Currently the buildds have installed: sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on binet.debian.org https://buildd.debian.org/status/fetch.php?pkg=linux&arch=amd64&ver=4.6.4-1&stamp=1468929143 https://buildd.debian.org/status/fetch.php?pkg=mutt&arch=amd64&ver=1.6.2-2&stamp=1471193283 to take examples from amd64 buildds. So in Debian we need to be able to build unstable on the buildds on a stable running system. It is the same in my case, my build host is running stable, but I build there both unstable and jessie (and when it was still supported even for wheezy). Hope this clarifies, Regards, Salvatore
