Log into moonbuild (10.1.10.11) and check out a tree. Below we check out a writable tree, because you'll probably end up making some changes:
- ssh -A username@10.1.10.11
- git clone username@moonshot.suchdamage.org:/srv/git/moonshot.git
+ ssh -A <username>@10.1.10.11
+ git clone <username>@moonshot.suchdamage.org:/srv/git/moonshot.git
this will leave you on the master branch of the [[Moonshot repository|branches]].
However, to build Debian test packages, you want to be on the debian branch. So:
git submodule update --init
Now, merge in the changes you want to test.
-Let's say that you're updating moonshot itself and that your changes are already on master.
+Let's say that you're updating moonshotUI and that your changes are already on master.
- cd moonshot
+ cd ui
git merge origin/master
Now we'll need to update the debian version number so we can do a fresh build:
This will pull up an editor. Describe the change. You will be modifying debian/changelog. We will not commit this file because we're just generating test packages.
+You probably want to run:
+
+ autoreconf -f -i
+
+To regenerate configure scripts.
+
Change back to the root of your checkout of the master repository.
Now, we want to disable stripping and optimization for our builds:
And run the builds
- ./debian-builder -s -c -s wheezy-i386 -s --arch=i386 -s -A directories
+ ./debian-builder -s -c -s wheezy-i386 -s --arch=i386 -s -A <directories>
The "-s" option gets repeated a lot because it passes the following option to sbuild, the Debian package build infrastructure. That will run an i386 (32-bit) build of the software using the wheezy-i386 (Debian 7.0) chroot (filesystem image). For directories include the directory of the software you're wishing to build.
+The build summary will have a status of "successful" if the build is successful. Most failures result in a status of "attempted".
+
The output packages will be placed in the debian_build directory.
Copy these to any test machines you like. You might like a loop something like