[Tails-dev] The future of Vagrant Tails builds [Was: Fwd: Bu…

Hi,

intrigeri wrote (29 Jun 2014 11:01:19 GMT) :
> it's now been made clear that the vagrant package in Debian needs
> help:

I gave a quick try at packaging the latest upstream release, and
failed (might be trivially fixable by anyone with some experience in
packaging Ruby stuff for Debian -- see Debian#741478 for details).

Note that Vagrant apparently doesn't support being used as a library
anymore; when trying to use our Rakefile with the latest Vagrant:

It appears that Vagrant was not properly loaded. Specifically,
the bundler context Vagrant requires was not setup. Please execute
vagrant using only the `vagrant` executable.

To sum up, if we want to keep Vagrant as the preferred build option
for Tails ISO, we'll need:

1. Someone who maintains the package in Debian.

2. Someone who maintains our own Vagrant-related stuff (starting with
converting the Rakefile stuff to using the `vagrant` executable,
and figuring out a sane way to upgrade the basebox).

3. To decide whether we really want+can support concurrent versions of
Vagrant; IMO, supporting the version in Debian testing/sid might be
manageable, but trying to achieve anything more ambitious seems
doomed to fail, considering the amount of work we've been able to
put into #1 and #2 recently.

Any idea if there's a good alternative to Vagrant, that requires less
work from us? Would e.g. Docker be an option? Can Gitian be used
without Vagrant, e.g. thanks to its LXC backend?

Cheers,
--
intrigeri