Re: Re: UEFI Secure Boot sprint report
Hi,
Thanks, your explanation is really helpful.
> The signing service is a source package builder.
It build source package but its source package is based on built binary package?
As I understand, singing to binary is necessary step.
1. source package
2. -> upload to dak
3. -> passed to buildd
4. -> binary package built
5. -> singing service pull those
6. -> source package built
7. -> dak, again
8. -> buildd, again
9. -> dak passes those to repo
And in previous report
> We're still missing (partially or completely):
> - generate a signing template for GRUB2
> - have DAK accept those generated source-only uploads
This is 7th step in above, right?
--
Regards,
Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Reply to: