path: root/dgit.1
diff options
authorIan Jackson <>2016-10-16 21:02:38 +0100
committerIan Jackson <>2016-10-23 17:01:38 +0100
commit37913654d58e03354aa4d5a6aa5afb9c5aeca6b7 (patch)
tree24a5ddf0218e0c4e8dfe876e242ad9b21762967c /dgit.1
parent8e9303a546371cfa631ff5f16ea4d7fdcfa6fad8 (diff)
Provide --force-unrepresentable.
Signed-off-by: Ian Jackson <>
Diffstat (limited to 'dgit.1')
1 files changed, 15 insertions, 0 deletions
diff --git a/dgit.1 b/dgit.1
index d6ac8b2..f7cbfbf 100644
--- a/dgit.1
+++ b/dgit.1
@@ -721,6 +721,21 @@ instead. Furthermore, the specified directory will be emptied,
removed and recreated before dgit starts, rather than removed
after dgit finishes. The directory specified must be an absolute
+.BI --force- something
+Instructs dgit to try to proceed despite detecting
+what it thinks is going to be a fatal problem.
+.B This is probably not going to work.
+These options are provided as an escape hatch,
+in case dgit is confused.
+(They might also be useful for testing error cases.)
+.B --force-unrepresentable
+Carry on even if
+dgit thinks that your git tree contains changes
+(relative to your .orig tarballs)
+which dpkg-source is not able to represent.
+Your build or push will probably fail later.
It is always possible with dgit to clone or fetch a package, make
changes in git (using git-commit) on the suite branch