Document in manpage under `dgit push' that it is best to build with dgit too.

diff --git a/debian/changelog b/debian/changelog
index b6dd3b28dfa64311b15abe8ddfefcc406a2566ec..480dd216f9ea43d7a15bd06c80a7040cd11f3c50 100644 (file)
--- 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.
 
   * 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
  --
 
 dgit (0.22.1) unstable; urgency=high

diff --git a/dgit.1 b/dgit.1
index a2f22f1495a54541a9dcff91cea6d1035b6a1321..260b742d8421efbd92c91ba7e2b08e63c64ce588 100644 (file)
--- 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
 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,
 
 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,