alphagov/packager — pull request #47 by mattbostock (2014-09-11 11:26:16+00:00)
Title: Use the GOV.UK dev VM box for Vagrant

Replace the Vagrant boxes obtained from `vagrantup.com` with the ones we
use for the GOV.UK development VM.

I hoped to use the official Ubuntu vagrant boxes[1], but they don't
appear to provide one compatible with VMWare Fusion which some of the
team use.

The development VM vagrant boxes provide more than is strictly necessary
for building packages, i.e. they install Puppet.

That said, they're likely to be better maintained (as we're using them
regularly) and using them results in one less Vagrant box to pull down
from the web.

The GOV.UK dev Vagrant box for Precise currently installs version
`4.3.14 r95030` of VirtualBox guest additions. The version installed by
the `vagrantup.com` box was `4.1.12_Ubuntu r77245`.

Note that this `Vagrantfile` has been tested with Virtualbox but not
VMWare Fusion.

The reason for replacing the `vagrantup.com` boxes is that the
VirtualBox guest additions it installed were seemingly no longer
compatible with my version of VirtualBox (`4.3.10r93012`). In
particular, I saw some odd behaviour seemingly caused by VirtualBox
shared folders:

```bash
vagrant@packager:~/packager$ rm -rf build/ruby-hiera-eyaml-2.0.2/
rm: cannot remove `build/ruby-hiera-eyaml-2.0.2/': Is a directory
```

`build_source.py` would also complain that
`build/ruby-hiera-eyaml-2.0.2/` already existed although checking for
that directory with `ls` on the VirtualBox host showed that the
directory did not in fact exist.