X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=tests%2Ftests%2Fquilt-gbp;h=cf148f613ee6f3b6ac150828cefa86154f579e69;hb=0060e3befbe283c90dcf6017ac8261168a6efe10;hp=b3e9534323f5928ee5a8fe9ca67d2e32bbc04b1a;hpb=cac3a7959fa4714480cac143f6d2e0f5758a12e5;p=dgit.git

diff --git a/tests/tests/quilt-gbp b/tests/tests/quilt-gbp
index b3e95343..cf148f61 100755
--- a/tests/tests/quilt-gbp
+++ b/tests/tests/quilt-gbp
@@ -2,52 +2,76 @@
 set -e
 . tests/lib
 
+# `dgit build-source` cleans before applying patches.  However, the
+# clean targets of 3.0 (quilt) packages are allowed to assume that
+# patches are applied.  If they are not, the clean targets can
+# misbehave in basically two ways:
+#
+# - fail to clean everything
+# - error out and stop the build
+#
+# In this test, what we want to see is whether dgit detects that quilt
+# fixup cannot be linear because the user has failed to pass --gbp.
+# So we need to ensure the package's clean target does not error out,
+# because that blocks dgit attempting quilt linearisation.  This
+# environment variable tells the example package's clean target not to
+# error out if it notices that patches have not yet been applied.
+export DGIT_TEST_TOLERATE_UNPATCHED_CLEAN=true
+
+t-tstunt-parsechangelog
+
 t-gbp-example-prep
 
 t-expect-fail 'quilt fixup cannot be linear' \
   t-dgit build-source
 
-t-dgit --quilt=gbp build-source
+t-git-config dgit-distro.test-dummy.dgit-tag-format new
+t-expect-fail 'requires split view so server needs to support' \
+t-dgit -wgf --quilt=gbp build-source
+t-newtag
+
+t-dgit --quilt=gbp --dgit-view-save=split.b1 build-source
+git rev-parse split.b1
 
-t-dgit --quilt=gbp --gbp=no-such-command-gbp build-source
+t-dgit --quilt=gbp --gbp-pq=no-such-command-gbp build-source
 
 echo spong >debian/pointless-for-dgit-test
 git add debian/pointless-for-dgit-test
 git commit -m Pointless
 
 t-expect-fail no-such-command-gbp \
-t-dgit --quilt=gbp --clean=git --gbp=no-such-command-gbp build-source
-
-t-dgit --quilt=gbp --clean=git build-source
+t-dgit --quilt=gbp --clean=git --gbp-pq=no-such-command-gbp build-source
 
-t-expect-fail 'specifies a different tree to your HEAD commit' \
-  t-dgit push
+test-push-1 () {
+	t-refs-same-start
+	t-ref-head
+}
 
-t-dgit --quilt=gbp push
+test-push-2 () {
+	t-dgit --quilt=gbp --dgit-view-save=split.p push
 
-exit 0
+	t-gbp-pushed-good
+}
 
-===
+test-push-1
 
-want to
+t-dgit --quilt=gbp --clean=git --dgit-view-save=split.b build-source
 
- t-pushed-good XXX need to do something more subtle than check our branch is in repo now
+t-expect-fail "HEAD specifies a different tree to $p" \
+  t-dgit push
 
- check that
-   - we didn't update caller's branch
+test-push-2
 
- do fetch
- check that this didn't update dgit remote ref
+echo wombat >>debian/pointless-for-dgit-test
+git add debian/pointless-for-dgit-test
+git commit -m 'Pointless 2'
 
- check that Dgit hash in dsc refers to tree identical
- to dpkg-source -x
+t-commit 'Check pseudomerge' 1.0-3
 
- check that that tree
-  - has patches applied (reuse rules build magic)
-  - has .gitignore edited
+test-push-1
 
-make a new change
+t-dgit --quilt=gbp --clean=git --dgit-view-save=split.b build-source
 
-push it
+test-push-2
 
-check that the synthetic fast forward worked
+t-ok