Fix Vagrant compatibility issue: cannot build after vm:up
Originally created by @anonym on #7134 (Redmine)
Taken from: https://mailman.boum.org/pipermail/tails-dev/2014-April/005574.html
This branch’s main purpose is to fix a compatibility issue between
“old”
and “new” Vagrant reported on tails-dev@ a while ago [1] that
prevents
doing something like:
rake vm:up
rake buildThe ‘build’ task doesn’t work if issued when the VM is already up,
because of VM API changes, so a “compabitility layer” is needed.
However, it works when a `build` is issued when the VM is not
up.
Since the code that fails in the former case is the cpu and memory
checks, it suggests that they are not done in the latter, which is
wrong. This branch also fixes that, so the checks are always
performed,
no matter the VM state.
[1] https://mailman.boum.org/pipermail/tails-dev/2014-February/005042.html
Feature Branch: bugfix/fix-vagrant-compatibility-issues