Re: bi-arch buildds and gpg keys

[Ansgar Burchardt <ansgar@debian.org>]

Hi,

Andreas Barth <aba@ayous.org> writes:
> as just discussed on IRC, we have some buildds building for more than
> one arch. In this case, I think it would be useful to use the same gpg
> key, and not have two different depending on the architecture being
> built.
>
> Currently we have: amd64-buildds also build i386. s390x-buildds
> also build s390.

Are the sets of buildds identical? Or are there amd64 (s390x) buildds
that do not built for i386 (s390) as well?

Allowing amd64-only buildds to upload i386 does grant more privileges,
but given we already have some buildds that can upload both
architectures I don't think we have to worry about this too much.

> So, can you please allow i386 packages signed by amd64, and s390
> packages signed by s390x? Thanks.

Done for both ftp- and security-master:

+---
| BEGIN;
| INSERT INTO acl_architecture_map (acl_id, architecture_id)
|   SELECT (SELECT id FROM acl WHERE name='buildd-all+amd64'),
|          (SELECT id FROM architecture WHERE arch_string='i386');
| INSERT INTO acl_architecture_map (acl_id, architecture_id)
|   SELECT (SELECT id FROM acl WHERE name='buildd-all+s390x'),
|          (SELECT id FROM architecture WHERE arch_string='s390');
| COMMIT;
+---

Ansgar