dgit: Do not use gdr to make patches with unmarked breakwater start

We must also adjust the gdr-fresh test case: now its patches are made
by dgit, not gdr.  We now check that they are correct (that is, that
dgit is now happy with things) but not what they look like).

Several other test cases test the dgit gdr makepatches functionality,
calling t-gdr-made-patches (via t-gdr-good, for example).  (I have
verified that changing the remaining "return 1" from branch_is_gdr to
"return 0" does cause many test failures.)

Closes: #1015779
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>

1 files changed, 7 insertions, 3 deletions

diff --git a/dgit b/dgit
index 1c5cef2..9acffa6 100755
--- a/dgit
+++ b/dgit
@@ -443,9 +443,13 @@ sub branch_is_gdr ($) {
 	    !defined git_cat_file "$walk~:debian" and
 	    !quiltify_trees_differ "$walk~", $walk
 	   ) {
-	    # (gdr classification of parent: BreakwaterStart
-	    printdebug "branch_is_gdr  $walk unmarked BreakwaterStart YES\n";
-	    return 1;
+	    # (gdr classification of parent: BreakwaterStart We cannot
+	    # process this using git-debrebase, because this can misrecognise
+	    # other kinds of branch contents, eg as in #1025451.  Not doing
+	    # this via gdr is OK, because the normal quilt linearisation will
+	    # do - doing it via gdr is just an optimisation.
+	    printdebug "branch_is_gdr  $walk unmarked BreakwaterStart NO\n";
+	    return 0;
 	}
 	# (gdr classification: Upstream Packaging Mixed Changelog)
 	printdebug "branch_is_gdr  $walk plain\n"