[Tails-dev] "boum"
Dear Sir/Madam, This is a registration agency, we are responsible for registering domain names and brand name. Our center received an application from Mcaper International Ltd and they apply to register boum as their brand name and some top-level domain names. We found the main body of domain names is same as your company name. I am not sure about the relationship between you and them. Please tell me whether or not your company authorizes them to register names. We are handling the application form and confirming with you if you authorize them or not ? If you don't authorize them, please give me an reply.Looking forward to your reply. Best Regards Gene Tang Tel: 0086.(0)551. 63491 193 Fax: 0086.(0)551. 63491 192 Address:No.2 Building,Wanda Square,WuHu Road,Hefei China ___ 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] Debian 9: Build fails consistently, name resolution fails sooner or later
On 03/11/2017 08:41 PM, anonym wrote: > Arnaud: >> --- a/vagrant/provision/setup-tails-builder >> +++ b/vagrant/provision/setup-tails-builder > [...] >> +# Configure apt to retry >> +echo 'APT::Acquire::Retries "20";' > /etc/apt/apt.conf.d/99retries > This will only affect provisioning, not any usage of APT during the build, > right? Or will it propagate into the chroot somehow? Indeed, it is not effective in the chroot. One way to set this setting in the chroot is to pass an option explicitly when running `lb config` (patch attached). Another way would be to add a file into the `config` directory, but I'm not sure exactly which file. According to today's live-build doc, creating a file `config/apt/apt.conf` should work. But it doesn't seem to match the existing layout, Tails already has a directory `config/chroot_apt`, maybe it's better to drop a file there, however I didn't try. Anyway. The fact is that it doesn't help me much, because apt-get **will not** retry when it's run along `apt-cacher-ng`. I strongly suspect that it's because apt-cacher-ng returns an error code 503 "Service Unavailable" on failure, instead of forwarding the original error code. I got in touch with apt-cacher-ng and let you know when I know more about that. Cheers --- auto/config | 1 + 1 file changed, 1 insertion(+) diff --git a/auto/config b/auto/config index 236ac0f1b9..d0b9c1a2e3 100755 --- a/auto/config +++ b/auto/config @@ -58,6 +58,7 @@ perl -pi \ # set Amnesia's general options $RUN_LB_CONFIG \ --verbose \ + --apt-options "--yes -oAcquire::Retries=20" \ --apt-recommends false \ --architecture amd64 \ --backports false \ -- 2.11.0 ___ 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?
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.