A couple of things come to mind:
1. Change the buildd code so that it downloads the keys for all relevant PPAs before starting.
2. You change your package to do it.
Both have heavy cons:
1. This will massively increase the load on the keyserver, which is already under tremendous strain (so I am told).
2. While this works for PPA packages, it's pretty nasty for rebuilds.
Thanks for the explanation Loïc. I have no idea either :(
It looks like it's happening because you're depending on: ppa.launchpad. net/ubuntu- toolchain- r/ppa/ubuntu maverick main
deb http://
in the sources.list.
A couple of things come to mind:
1. Change the buildd code so that it downloads the keys for all relevant PPAs before starting.
2. You change your package to do it.
Both have heavy cons:
1. This will massively increase the load on the keyserver, which is already under tremendous strain (so I am told).
2. While this works for PPA packages, it's pretty nasty for rebuilds.
More ideas would be good here.