This is an automated email from the git hooks/post-receive script. guillem pushed a commit to branch main in repository dpkg.
View the commit online: https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=eb7ade60e774dec9cca8ca7f0f8e6d916f076627 commit eb7ade60e774dec9cca8ca7f0f8e6d916f076627 Author: Guillem Jover <[email protected]> AuthorDate: Tue May 16 23:30:12 2023 +0200 man: Mention .buildinfo in dpkg-buildpackage --sign-command description The signing involves also the .buildinfo file, which was not mentioned here. --- man/dpkg-buildpackage.pod | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/man/dpkg-buildpackage.pod b/man/dpkg-buildpackage.pod index 3d7fb2313..3da341992 100644 --- a/man/dpkg-buildpackage.pod +++ b/man/dpkg-buildpackage.pod @@ -605,10 +605,12 @@ The specific OpenPGP backends supported in order of preference are: =item B<-p>, B<--sign-command=>I<sign-command> When B<dpkg-buildpackage> needs to execute an OpenPGP backend command to -sign a source control (B<.dsc>) file or a B<.changes> file it will run +sign a source control (B<.dsc>) file, a B<.buildinfo> file or a B<.changes> +file it will run I<sign-command> (searching the B<PATH> if necessary) instead of the default or auto-detected backend command (long option since dpkg 1.18.8). -I<sign-command> will get all the arguments defined by the B<--sign-backend>. +I<sign-command> will get all the backend specific arguments according to +the B<--sign-backend> selected. I<sign-command> should not contain spaces or any other shell metacharacters. =item B<-k>, B<--sign-keyid=>I<key-id> -- Dpkg.Org's dpkg
