On 03/21/2017 02:05 PM, anonym wrote:
> Austin English:
>> Hi all,
>>
>> It's been a while since I've built tails, been busy with other
>> projects.. Anyway, I've done a git pull, git clean -fxd (to clear out
>> .vagrant), and removed ~/.vagrant.d. I then tried to build with noram,
>> since my laptop is low on free memory, and I get:
>>
>> austin@debian-laptop:~/src/tails$ export TAILS_BUILD_OPTIONS=noram
>>
>> austin@debian-laptop:~/src/tails$ rake build
>> rake aborted!
>> VagrantCommandError: 'vagrant ["status"]' command failed: 1
>> /home/austin/src/tails/Rakefile:61:in `capture_vagrant'
>> /home/austin/src/tails/Rakefile:84:in `vm_state'
>> /home/austin/src/tails/Rakefile:117:in `enough_free_memory_for_ram_build?'
>> /home/austin/src/tails/Rakefile:145:in `block in <top (required)>'
>> Tasks: TOP => build => parse_build_options
>> (See full trace by running task with --trace)
>
> Weird! What happens if you run:
>
> (cd vagrant && vagrant status)
>
> Also, have you made sure that up-to-date packages of vagrant and vagrant-libvirt are installed? (I know some people have had APT pinnings and stuff that has kept them on old, unsupported versions.)
>
> I'd also be interested if one of our development branches, where we've reworked a lot how Vagrant works, improves the situation; can you please checkout the wip/11972-use-vagrant-in-jenkins Git branch and try to build? You might have to clear vagrant/.vagrant before you try starting this new VM.
>
> Cheers!
Thanks for the tip, apparently vagrant-libvirt got uninstalled somehow
and I missed that. After installing, I had to fiddle with
vagrant/libvirt a bit to get the build vm up and in a good state, but
after that, seems to be working now.
Thanks anonym!
--
-Austin
GPG: 14FB D7EA A041 937B
