Re: [Tails-dev] Can't build tails, not enough ram?

2017-03-22 Thread Austin English
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 '
>> 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



signature.asc
Description: OpenPGP digital signature
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Can't build tails, not enough ram?

2017-03-21 Thread anonym
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 '
> 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!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Can't build tails, not enough ram?

2017-03-12 Thread 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 '
Tasks: TOP => build => parse_build_options
(See full trace by running task with --trace)

I see the same thing when I build on my desktop, with ~15 GB free (with
or without noram), so I feel like I've done something wrong.

I've followed https://tails.boum.org/contribute/build/, but don't see
any workarounds for this. Anyone have any idea what I'm missing?

This is on Debian Sid, x86_64.

-- 
-Austin
GPG: 14FB D7EA A041 937B
austin@debian-laptop:~$ dpkg -l | grep -e rake -e libvirt -e dnsmasq-base -e 
ebtables -e qemu -e vagrant
ii  dnsmasq-base   2.76-5   
 amd64Small caching DNS proxy and DHCP/TFTP server
ii  ebtables   2.0.10.4-3.5 
 amd64Ethernet bridge frame table administration
ii  gir1.2-libvirt-glib-1.0:amd64  1.0.0-1  
 amd64GObject introspection files for the libvirt-glib library
ii  ipxe-qemu  1.0.0+git-20161027.b991c67-1 
 all  PXE boot firmware - ROM images for qemu
ii  libvirt-bin1.3.1-1  
 amd64Dummy transitional package
ii  libvirt-clients3.0.0-2  
 amd64Programs for the libvirt library
ii  libvirt-daemon 3.0.0-2  
 amd64Virtualization daemon
ii  libvirt-daemon-system  3.0.0-2  
 amd64Libvirt daemon configuration files
ii  libvirt-glib-1.0-0:amd64   1.0.0-1  
 amd64libvirt GLib and GObject mapping library
ii  libvirt0   3.0.0-2  
 amd64library for interfacing with different virtualization systems
ii  python-libvirt 3.0.0-2  
 amd64libvirt Python bindings
ii  qemu-efi   0~20161202.7bbe0b3e-1
 all  UEFI firmware for 64-bit ARM virtual machines
ii  qemu-kvm   1:2.8+dfsg-2 
 amd64QEMU Full virtualization on x86 hardware
ii  qemu-slof  20161019+dfsg-1  
 all  Slimline Open Firmware -- QEMU PowerPC version
ii  qemu-system1:2.8+dfsg-2 
 amd64QEMU full system emulation binaries
ii  qemu-system-arm1:2.8+dfsg-2 
 amd64QEMU full system emulation binaries (arm)
ii  qemu-system-common 1:2.8+dfsg-2 
 amd64QEMU full system emulation binaries (common files)
ii  qemu-system-mips   1:2.8+dfsg-2 
 amd64QEMU full system emulation binaries (mips)
ii  qemu-system-misc   1:2.8+dfsg-2 
 amd64QEMU full system emulation binaries (miscellaneous)
ii  qemu-system-ppc1:2.8+dfsg-2 
 amd64QEMU full system emulation binaries (ppc)
ii  qemu-system-sparc  1:2.8+dfsg-2 
 amd64QEMU full system emulation binaries (sparc)
ii  qemu-system-x861:2.8+dfsg-2 
 amd64QEMU full system emulation binaries (x86)
ii  qemu-utils 1:2.8+dfsg-2 
 amd64QEMU utilities
ii  rake   10.5.0-2 
 all  ruby make-like utility
ii  vagrant1.9.1+dfsg-1 
 all  Tool for building and distributing virtualized development 
environments




signature.asc
Description: OpenPGP digital signature
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.