Yeah, without inserting the keys it fails at apt-get -y install apt-cacher-ng in setup-tails-builder
These keys could easily be added into the shared folder created during tails setup. The Debian key ring wanted to install an additional 40 MB and I found this path much easier. Log: Get:1 http://security.debian.org squeeze/updates Release.gpg [836 B] Ign http://security.debian.org/ squeeze/updates/main Translation-en Ign http://security.debian.org/ squeeze/updates/main Translation-en_US Get:2 http://security.debian.org squeeze/updates Release [86.9 kB] Get:3 http://security.debian.org squeeze/updates/main Sources [131 kB] Get:4 http://security.debian.org squeeze/updates/main amd64 Packages [347 kB] Get:5 http://cdn.debian.net squeeze Release.gpg [1,672 B] Ign http://cdn.debian.net/debian/ squeeze/main Translation-en Ign http://cdn.debian.net/debian/ squeeze/main Translation-en_US Get:6 http://cdn.debian.net squeeze-updates Release.gpg [836 B] Ign http://cdn.debian.net/debian/ squeeze-updates/main Translation-en Ign http://cdn.debian.net/debian/ squeeze-updates/main Translation-en_US Get:7 http://cdn.debian.net unstable Release.gpg [836 B] Get:8 http://cdn.debian.net/debian/ unstable/main Translation-en [4,429 kB] Ign http://cdn.debian.net/debian/ unstable/main Translation-en_US Get:9 http://cdn.debian.net squeeze Release [99.8 kB] Get:10 http://cdn.debian.net squeeze-updates Release [113 kB] Get:11 http://cdn.debian.net unstable Release [205 kB] Err http://cdn.debian.net squeeze-updates Release Ign http://cdn.debian.net unstable Release Get:12 http://cdn.debian.net squeeze/main Sources [4,541 kB] Get:13 http://cdn.debian.net squeeze/main amd64 Packages [6,538 kB] Get:14 http://cdn.debian.net unstable/main amd64 Packages [6,670 kB] Get:15 http://backports.debian.org squeeze-backports Release.gpg [836 B] Get:16 http://backports.debian.org/debian-backports/ squeeze-backports/main Translation-en [246 kB] Ign http://backports.debian.org/debian-backports/ squeeze-backports/main Translation-en_US Get:17 http://backports.debian.org squeeze-backports Release [109 kB] Err http://backports.debian.org squeeze-backports Release Fetched 23.5 MB in 11s (2,118 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: avahi-daemon cpp-4.4 dbus ed g++-4.4 gcc-4.4 gcc-4.4-base gcc-4.8-base init-system-helpers libavahi-common-data libavahi-common3 libavahi-core7 libc-dev-bin libc6 libc6-dev libdaemon0 libdbus-1-3 libgcc1 libgmp10 libgomp1 liblzma5 libmpfr4 libnss-mdns libstdc++6 libstdc++6-4.4-dev libsystemd-login0 linux-headers-2.6.32-5-common locales make multiarch-support Suggested packages: doc-base libfuse2 avahi-autoipd gcc-4.4-locales dbus-x11 g++-4.4-multilib gcc-4.4-doc libstdc++6-4.4-dbg gcc-4.4-multilib libmudflap0-4.4-dev libgcc1-dbg libgomp1-dbg libmudflap0-dbg libcloog-ppl1 libppl-c4 libppl12 glibc-doc libstdc++6-4.4-doc make-doc The following packages will be REMOVED: gcc-4.3 linux-headers-2.6-amd64 linux-headers-2.6.32-5-amd64 logrotate The following NEW packages will be installed: apt-cacher-ng avahi-daemon dbus ed gcc-4.8-base init-system-helpers libavahi-common-data libavahi-common3 libavahi-core7 libdaemon0 libdbus-1-3 libgmp10 liblzma5 libnss-mdns libsystemd-login0 multiarch-support The following packages will be upgraded: cpp-4.4 g++-4.4 gcc-4.4 gcc-4.4-base libc-dev-bin libc6 libc6-dev libgcc1 libgomp1 libmpfr4 libstdc++6 libstdc++6-4.4-dev linux-headers-2.6.32-5-common locales make 15 upgraded, 16 newly installed, 4 to remove and 254 not upgraded. Need to get 24.9 MB of archives. After this operation, 532 kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! libc-dev-bin gcc-4.4-base gcc-4.8-base multiarch-support locales libc6 libgmp10 libmpfr4 cpp-4.4 libgcc1 libgomp1 gcc-4.4 libstdc++6 g++-4.4 libstdc++6-4.4-dev make libc6-dev liblzma5 init-system-helpers apt-cacher-ng libavahi-common-data libavahi-common3 libavahi-core7 libdbus-1-3 libsystemd-login0 dbus avahi-daemon ed libnss-mdns Stderr from the command: stdin: is not a tty W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://cdn.debian.net squeeze-updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 W: GPG error: http://cdn.debian.net unstable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://backports.debian.org squeeze-backports Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 W: Failed to fetch http://cdn.debian.net/debian/dists/squeeze-updates/Release W: Failed to fetch http://backports.debian.org/debian-backports/dists/squeeze-backports/Release W: Some index files failed to download, they have been ignored, or old ones used instead. E: There are problems and -y was used without --force-yes /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/plugins/communicators/ssh/communicator.rb:85:in `execute' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/plugins/provisioners/shell/provisioner.rb:33:in `block (2 levels) in provision' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/plugins/provisioners/shell/provisioner.rb:16:in `tap' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/plugins/provisioners/shell/provisioner.rb:16:in `block in provision' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/plugins/provisioners/shell/provisioner.rb:90:in `with_script_file' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/plugins/provisioners/shell/provisioner.rb:14:in `provision' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/builtin/provision.rb:74:in `run_provisioner' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/builtin/provision.rb:62:in `block in call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/builtin/provision.rb:58:in `each' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/builtin/provision.rb:58:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:13:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/plugins/providers/virtualbox/action/set_name.rb:47:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:51:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:51:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:51:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:57:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:57:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/builder.rb:116:in `call' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/machine.rb:147:in `action' /usr/lib/ruby/gems/2.0.0/gems/vagrant-1.3.5/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run' Tasks: TOP => build => vm:up On Tue, Dec 17, 2013 at 3:12 PM, intrigeri <[email protected]> wrote: > Hi, > > jvoisin wrote (17 Dec 2013 19:19:28 GMT) : > > On 12/17/2013 03:45 PM, David Wolinsky wrote: > >> Use this before rake build > >> export TAILS_BUILD_OPTIONS="noproxy" > >> then rake build > > Tails successfully built from scratch, in less than 2h30. > > Your patch is working :) > > Thank you for testing. I have pushed David's patch, with the suggested > s/2/3/ change that was required to support Julien's Vagrant 1.2.2, to > the bugfix/6221-support-newer-vagrant branch. > > I can't merge it yet, as this addition to > vagrant/provision/setup-tails-builder is clearly unsafe: > > > for num in 5 6 7; do > > wget http://ftp-master.debian.org/keys/archive-key-"$num".0.asc > > apt-key add archive-key-"$num".0.asc > > rm archive-key-"$num".0.asc > > done > > I'm curious why this would be necessary: Tails itself is based on > Squeeze too, includes the unstable APT sources too, and does not need > any such kludge. > > Worst case, we will bundle the needed keys in our Git repository, or > (better) install a newer debian-archive-keyring package from Wheezy, > or something. > > David, I read "Added the insertion of the Debian keys because it was > failing to build otherwise" in your commit message. May you please > retry without thes bits, and tell us exactly how it fails? > > Cheers, > -- > intrigeri > | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc > | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc > _______________________________________________ > tails-dev mailing list > [email protected] > https://mailman.boum.org/listinfo/tails-dev >
_______________________________________________ tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev
