Hello, On Sat, Aug 20, 2016 at 06:56:59PM +0200, Johannes Schauer wrote: > another way would be to change propellor not to run $(sbuild-update --keygen) > anymore at all. Doing this is only required if you want to use sbuild for > chroots containing Debian squeeze or older. If you only build for newer Debian > releases, then signing the internal dummy repository will serve no purpose > other than making your builds slower and requiring lots of entropy during the > one-time setup... > > You might want to open another bug against propellor to ask it not to generate > the key anymore if the propellor maintainers agree that that they don't want > to > support squeeze chroots anymore.
We've got one open here: http://propellor.branchable.com/todo/updates_for_sbuild_0.70.0-1/ > Also note, that there is a possibility that I will mark this bug as > wontfix. For a reasoning, please refer to the thread on debian-devel > starting at [1]. Ah, good to know about that possibility. -- Sean Whitton
signature.asc
Description: PGP signature
