[D-m-team] Creating changesets

[Joey Hess]

Anthony Towns wrote:
> Making keycheck grab signatures off the keyserver seems easy enough. And
> potentially useful in case a key's been revoked since the changeset was
> originally created.

Would miss signatures that were never uploaded to a keyserver of course.
Also needs network, which most of the rest can be done without.

(keycheck should already notice revocations of DD keys since it does work
against a keyring from the keyserver.)

> Thinking out loud, wouldn't stripping signatures also make for a
> smaller DM keyring?

Somewhat smaller, of course.

> That seems like a good thing if we have lots of
> DMs eventually; the DD keyring is a bit unweildy, in particular, and in
> theory we're hoping to make something that'll work for maintaining it too.

I hope the DM keyring never reaches the same scale as the DD keyring. 24 MB
size isn't really that bad for the DD keyring, the main unweidlyness is the
sheer number of keys in it. Of course, I did build jetring based on
manipulating it, which is why jeyring has eg, the ability to fast-forward when
rebuilding a keyring.

> Well, maybe it should fill in Created-By: and leave Changed-By: for
> the DM maintainer that commits the key.

Ah, if this is being run by the applicant, and not by us, then yes, it should
do that.

> Or maybe we should make that
> Committed-By:?  Or maybe we should just use revision history for that
> and drop the committer name from the changeset entirely?

We could, but then you can't tell what went on by examining the source
package, which I think is currently a good feature.
 
> Or we could add the committer name automatically when we do keycheck,
> I guess.

Yes, or have a ./accept script that does it.

-- 
see shy jo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/d-m-team/attachments/20071119/18110c4a/attachment-0001.pgp