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

Delete this message

Reply to this message
Author: BS
Date:  
To: tails-dev
Subject: [Tails-dev] The future of Vagrant Tails builds [Was: Fwd: Bug#753095: RFH: vagrant]
I must admit, I'm pretty confused. I thought the docs stated that
wheezy was the only environment which
Tails would build in. If that's not the case, how is Tails building Tails?

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

help:
> 1. Someone who maintains the package in Debian.


Is that an absolute requirement? What about downloading from vagrant's
'legacy' page
http://downloads.vagrantup.com/
http://downloads.vagrantup.com/tags/v1.3.5
http://files.vagrantup.com/packages/a40522f5fabccb9ddabad03d836e120ff5d14093/vagrant_1.3.5_i686.deb

> 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.


Concurrent version support seems impossible.

> 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?


Docker is available in jessie, but not as a back port. It's also
limited to amd64 machines,
because it uses go. The go team are working on a 32 bit version, but I
don't know how stable
that would be. Also, FWIW, the docker team says you shouldn't use
docker in production. I assume
Tails counts itself as "production"? (also
http://blog.docker.com/2013/08/containers-docker-how-secure-are-they/)

I'm full of assumptions, like wheezy is the OS you want to build on,
(why build squeeze on wheezy?)
but I think this makes sense:

1) Rebuild the squeeze.box with the version of vagrant available on wheezy
     This may resolve current box add issues on wheezy and may buy  
some time. It does not seem like a permanent solution.
2) Move the vagrant related Rakefile code into the vagrant file or use  
the vagrant CLI, where appropriate
     This should allow for easier upgrades, and the opportunity to  
explore other versions of vagrant





-------------------------------------------------

VFEmail.net - http://www.vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!