Change scenario tests to use version 3.2-1

This is purely for aesthethics. I prefer to have unique version number
components, so 3 is better than 1, since the Debian version is 1.

2 files changed, 10 insertions, 10 deletions

diff --git a/doc/060-cleanly.yarn b/doc/060-cleanly.yarn
index c7045cc..167e171 100644
--- a/doc/060-cleanly.yarn
+++ b/doc/060-cleanly.yarn
@@ -13,13 +13,13 @@ The first thing we need to do is determine, preferably automatically,
 what the name of the project is and what its version is.
 
     SCENARIO cleanly performs pipeline steps
-    GIVEN a source code repository for project foo version 1.2-1
+    GIVEN a source code repository for project foo version 3.2-1
 
     WHEN user runs, in foo, cleanly get-name
     THEN the output is "foo\n"
 
     WHEN user runs, in foo, cleanly get-upstream-version
-    THEN the output is "1.2\n"
+    THEN the output is "3.2\n"
 
 ## Create upstream release tar archive
 
@@ -27,7 +27,7 @@ We create a tar archive by extracing the source code from git. The
 operation needs to know the upstream name and version number.
 
     WHEN user runs, in foo, cleanly tarball
-    THEN file foo-1.2.tar.xz exists
+    THEN file foo-3.2.tar.xz exists
 
 ## Create Debian source package
 
@@ -37,9 +37,9 @@ Debian version part is just 1. (FIXME: This will need to be made more
 flexible later.)
 
     WHEN user runs, in foo, cleanly dsc
-    THEN file foo_1.2.orig.tar.xz exists
-    AND file foo_1.2-1.debian.tar.xz exists
-    AND file foo_1.2-1.dsc exists
+    THEN file foo_3.2.orig.tar.xz exists
+    AND file foo_3.2-1.debian.tar.xz exists
+    AND file foo_3.2-1.dsc exists
 
 ## Build a Debian binary package
 
@@ -48,4 +48,4 @@ package, given a source package. (Note that for this, we fake the
 actual build to avoid having to have `root` access.)
 
     WHEN user runs, in foo, cleanly deb
-    THEN file foo_1.2-1_all.deb exists
+    THEN file foo_3.2-1_all.deb exists
diff --git a/doc/070-pipeline.yarn b/doc/070-pipeline.yarn
index 7a7e85d..b4cc732 100644
--- a/doc/070-pipeline.yarn
+++ b/doc/070-pipeline.yarn
@@ -8,7 +8,7 @@ we have the necessary access to localhost.
 
 First of all, we need a git repository with some source code.
 
-    GIVEN a source code repository for project foo version 1.2-1
+    GIVEN a source code repository for project foo version 3.2-1
 
 Then we need an Ick file.
 
@@ -21,5 +21,5 @@ Then we need an Ick file.
 Then we do the build.
 
     WHEN user runs ick foo.ick
-    THEN the APT repository for foo.ick contains foo_1.2-1.dsc
-    THEN the APT repository for foo.ick contains foo_1.2-1_all.deb
+    THEN the APT repository for foo.ick contains foo_3.2-1.dsc
+    THEN the APT repository for foo.ick contains foo_3.2-1_all.deb