Bug#593611: Clarify whose signature should go in debian/changelog (4.4)
- To: Dimitri John Ledkov <dimitri.ledkov@surgut.co.uk>
- Cc: 593611@bugs.debian.org, Bill Allombert <ballombe@debian.org>
- Subject: Bug#593611: Clarify whose signature should go in debian/changelog (4.4)
- From: Russ Allbery <rra@debian.org>
- Date: Sat, 02 Aug 2014 12:16:39 -0700
- Message-id: <[🔎] 87lhr61z3c.fsf@windlord.stanford.edu>
- Reply-to: Russ Allbery <rra@debian.org>, 593611@bugs.debian.org
- In-reply-to: <CANBHLUh6zT9W-P=G93iFVUAoFgRvD-vNPTkFr_NteeD_5m=+GQ@mail.gmail.com> (Dimitri John Ledkov's message of "Wed, 30 Jul 2014 14:35:10 +0100")
- References: <20100819161922.3287.54372.reportbug@pcfelipe.sateler> <handler.593611.B.12822347734102.ack@bugs.debian.org> <4C6D5C4A.8010805@debian.org> <87ocbuz831.fsf_-_@windlord.stanford.edu> <20100922123956.GA16412@yellowpig> <87pqfc32x1.fsf@windlord.stanford.edu> <20140303132423.GA6027@yellowpig> <20140730130836.GA25023@yellowpig> <CANBHLUh6zT9W-P=G93iFVUAoFgRvD-vNPTkFr_NteeD_5m=+GQ@mail.gmail.com>
Dimitri John Ledkov <dimitri.ledkov@surgut.co.uk> writes:
> Imho, we should be making it less ambigious and adjusting our
> generated changes and/or debian/changelog to more team maintained
> workflows:
> We should unambigiously document:
> Maintainer: Typically team (list of names)
> Uploads: Typically a subset of team members (list of names)
> Changed-by: everyone who contributed changes in this upload (list of names)
> Signed-by: person who signed and dput (single uid fingerprint, not
> sure we support multi-signed uploads)
> GPG Signature itself, should match fingerprint of Singed-by uid
> The format of debian/changelog at the moment enforces only one name
> and it has no mapping to expose all people involved.
> "multi-maintainer changelog" convention of using [ Name [<email>] ] is
> good, but is still currently defeated by current single sign-off line
> which propagates to Changed-by.
I think this would be an interesting direction in which to take things,
but it's a larger project that requires changing the definition of fields
(Maintainer is currently single-valued) and how various tools work. If
you or someone else wanted to pursue this, I think it would be a more
accurate representation in the long run, but it may be more effort than is
warranted. In the meantime, in the short run, I think we should clarify
the wording to something a bit closer to what people normally do.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: