|author||Ian Jackson <email@example.com>||2015-06-30 21:02:38 +0100|
|committer||Ian Jackson <firstname.lastname@example.org>||2015-06-30 21:02:38 +0100|
Provide example workflow for dgit rpush. Closes:#763334.
2 files changed, 13 insertions, 1 deletions
diff --git a/debian/changelog b/debian/changelog
index a6353e1..7969a61 100644
@@ -75,6 +75,8 @@ dgit (0.23~) unstable; urgency=low
* Detect and bomb out on vendor-specific `3.0 (quilt)' patch series.
+ * Provide example workflow for dgit rpush. Closes:#763334.
dgit (0.22.1) unstable; urgency=high
@@ -167,7 +167,17 @@ Pushes the contents of the specified directory on a remote machine.
This is like running dgit push on build-host with build-dir as the
current directory; however, signing operations are done on the
invoking host. This allows you to do a push when the system which has
-the source code and the build outputs has no access to the key.
+the source code and the build outputs has no access to the key:
+1. Clone on build host (dgit clone)
+2. Edit code on build host (edit, git commit)
+3. Build package on build host (dgit build)
+4. Test package on build host or elsewhere (dpkg -i, test)
+5. Upload by invoking dgit rpush on host with your GPG key.
However, the build-host must be able to ssh to the dgit repos. If
this is not already the case, you must organise it separately, for