From 1b99def96ddbaec91a0208916f257a1381e446b6 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Sun, 23 Oct 2016 21:16:11 +0100 Subject: [PATCH] import-dsc: Document --require-valid-signature Signed-off-by: Ian Jackson --- dgit.1 | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/dgit.1 b/dgit.1 index 2c583fe8..5367c36a 100644 --- a/dgit.1 +++ b/dgit.1 @@ -240,7 +240,7 @@ other kinds of more exotic history. If dgit can't find a suitable linearisation of your history, by default it will fail, but you can ask it to generate a single squashed patch instead. .TP -\fBdgit import-dsc\fR \fI../path/to/.dsc\fR [\fB+\fR|\fB..\fR]branch +\fBdgit import-dsc\fR [\fIsub-options\fR] \fI../path/to/.dsc\fR [\fB+\fR|\fB..\fR]branch Import a Debian-format source package, specified by its .dsc, into git, @@ -257,6 +257,14 @@ and it therefore does not make a pseudomerge to bind the import into any existing git history. +There is only only sub-option: + +.B --require-valid-signature +causes dgit to insist that the signature on the .dsc is valid +(using the same criteria as dpkg-source -x). +Otherwise, dgit tries to verify the signature but +the outcome is reported only as messages to stderr. + If .I branch is prefixed with -- 2.30.2