Roger Leigh <rle...@codelibre.net> (29/12/2010): > This is a one-time only event. Once the key is generated (which you > can do with "sbuild-update -k" on another system or outside a > package build at your leisure) the same key will be used for all > subsequent builds.
One-time.. per host? Or per chroot? > The current strategy is to allow you to generate your own key and > put it in place. If you haven't done that, it will autogenerate one > the first time it's needed. For buildds, you'll probably want to > generate one elsewhere and copy it cover. Note this is in the > release notes (NEWS.gz) for release 0.60.6. Which apt-listchanges doesn't show, so.. > If you have any thoughts on how we can do this better, that would be > great. apt and aptitude want the local archive signing, so we do it > for that. If using the "internal" resolver, no key is needed. Since you changed the default (which is another story, sigh), I'm not using the internal resolver anymore. KiBi.
signature.asc
Description: Digital signature
