Hi, Quoting Christian Hofstaedtler (2016-07-16 14:38:17) > recently apt has stopped depending on gnupg; as such it is not installed any > more in the chroot created by sbuild-createchroot. > > But then at build time, sbuild wants gpg to create the APT archive and > aborts.
on the other hand... having thought about this for a bit longer, maybe a better solution than increasing the size of the list of manual "build essential" packages, this would be a good time to get rid of gnupg inside the chroot. The only reason gnupg support still exists is for old-old-stable (squeeze) chroots. I do not see another reason why one would want to sign the internal repository. So maybe a better fix for this problem would be to add a helpful warning message which instructs users how to fix the situation. Which is by either: - deleting /var/lib/sbuild/apt-keys if they don't build for squeeze - by adding "gnupg:native" to the $core_depends options in their ~/.sbuildrc if they want to build for squeeze The advantage would be that the chroots source packages will be built in will be more minimal which in turn will for example allow finding source packages that should build depend on gnupg but forgot to explicitly do so. For reasons of this kind, we should not install extra packages into the chroot unless absolutely needed. I'm not convinced whether this need exists in this situation. What do you think? Thanks! cheers, josch
signature.asc
Description: signature
