From 660cbb30600507979b3a43a346bcf18901130085 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Tue, 25 Nov 2014 15:19:08 +0000 Subject: [PATCH] Document in manpage under `dgit push' that it is best to build with dgit too. --- debian/changelog | 3 +++ dgit.1 | 5 ++++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index b6dd3b28..480dd216 100644 --- a/debian/changelog +++ b/debian/changelog @@ -54,6 +54,9 @@ dgit (0.23~) unstable; urgency=low * Reject (rather than ignoring) further options merged witht -wn, -wg, -wd. + * Document in manpage under `dgit push' that it is best to build with + dgit too. Closes:#763333. + -- dgit (0.22.1) unstable; urgency=high diff --git a/dgit.1 b/dgit.1 index a2f22f14..260b742d 100644 --- a/dgit.1 +++ b/dgit.1 @@ -143,7 +143,10 @@ Tagging, signing and actually uploading should be left to dgit push. Does an `upload', pushing the current HEAD to the archive (as a source package) and to dgit-repos (as git commits). The package must already have been built ready for upload, with the .dsc and .changes -left in the parent directory. +left in the parent directory. It is normally best to do the build +with dgit too (eg with dgit sbuild): some existing build tools pass +unhelpful options to dpkg-source et al by default, which can result in +the built source package not being identical to the git tree. In more detail: dgit push checks that the current HEAD corresponds to the .dsc. It then pushes the HEAD to the suite's dgit-repos branch, -- 2.30.2