Building an ISO as documented can fail in many ways

I have been working on building Tails for Wheezy as outlined here:

https://tails.boum.org/contribute/build/

The package list likely needs to be updated from:

sudo apt-get install virtualbox rake vagrant/unstable \
  ruby-childprocess/jessie ruby-net-scp/jessie ruby-net-ssh/jessie

To this list with git-core included:

sudo apt-get install git-core virtualbox rake vagrant/unstable \
  ruby-childprocess/jessie ruby-net-scp/jessie ruby-net-ssh/jessie

I would also suggest that a default Wheezy system needs to be modified to include the following lines inside of /etc/apt/sources.list:

deb http://ftp.de.debian.org/debian/ squeeze jessie contrib non-free
deb-src http://ftp.de.debian.org/debian/ squeeze jessie contrib non-free
deb http://ftp.de.debian.org/debian/ squeeze sid contrib non-free
deb-src http://ftp.de.debian.org/debian/ squeeze sid contrib non-free

After I had those lines, I pinned the packages by creating three pinning files:

security.pref
stable.pref
testing.pref
unstable.pref

security.pref contains:

Package: *
Pin: release 1=Debian-Security
Pin-Priority: 1000

stable.pref contains:

Package: *
Pin: release a=stable
Pin-Priority: 995

testing.pref contains:

Package: *
Pin: release a=testing
Pin-Priority: 750

unstable.pref contains:

Package: *
Pin: release a=unstable
Pin-Priority: 50

Once all of those things are setup, I performed the usual apt-get update and did the installs like so:

sudo apt-get install git-core virtualbox rake vagrant/unstable \
  ruby-childprocess/jessie ruby-net-scp/jessie ruby-net-ssh/jessie

I then performed the following commands:

git clone git://git.tails.boum.org/tails
cd tails
git checkout devel
export TAILS_BUILD_OPTIONS="noproxy"
rake build

The rake build of downloading the .box file (tails-builder-20140709.box) surprised me a bit. How is this verified?

I ask becuase I had an issue during rake build time:


error@vula:~/Documents/tails$ time rake build
No HTTP proxy set.

This is the first time that the Tails builder virtual machine is
started. The virtual machine template is about 300 MB to download,
so the process might take some time.

Please remember to shut the virtual machine down once your work on
Tails is done:

    $ rake vm:halt

Bringing machine 'default' up with 'virtualbox' provider...
[default] Box 'tails-builder-20140709' was not found. Fetching box from specified URL for
the provider 'virtualbox'. Note that if the URL does not have
a box for this provider, you should interrupt Vagrant now and add
the box yourself. Otherwise Vagrant will attempt to download the
full box prior to discovering this error.
Downloading box from URL: http://dl.amnesia.boum.org/tails/project/vagrant/tails-builder-20140709.box
Extracting box...te: 2314k/s, Estimated time remaining: --:--:--)B
Successfully added box 'tails-builder-20140709' with provider 'virtualbox'!
[default] Importing base box 'tails-builder-20140709'...
rake aborted!
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "/home/error/.vagrant.d/boxes/tails-builder-20140709/virtualbox/box.ovf"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/error/.vagrant.d/boxes/tails-builder-20140709/virtualbox/box.ovf...
OK.
0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: <vbox:Machine> element in OVF contains a medium attachment for the disk image a965b45c-0500-48de-9e31-c7999cdf19fa but the OVF describes no such image
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Appliance, interface IAppliance, callee 
Context: "ImportAppliance" at line 793 of file VBoxManageAppliance.cpp

Tasks: TOP => build => vm:up
(See full trace by running task with --trace)

real    2m33.792s
user    0m6.684s
sys 0m5.816s

I re-ran the rake command with --trace and had the same issue:

time rake build --trace
** Invoke build (first_time)
** Invoke parse_build_options (first_time)
** Execute parse_build_options
** Invoke ensure_clean_repository (first_time)
** Execute ensure_clean_repository
** Invoke validate_http_proxy (first_time)
** Execute validate_http_proxy
No HTTP proxy set.
** Invoke vm:up (first_time)
** Invoke parse_build_options 
** Invoke validate_http_proxy 
** Execute vm:up

This is the first time that the Tails builder virtual machine is
started. The virtual machine template is about 300 MB to download,
so the process might take some time.

Please remember to shut the virtual machine down once your work on
Tails is done:

    $ rake vm:halt

Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'tails-builder-20140709'...
rake aborted!
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "/home/error/.vagrant.d/boxes/tails-builder-20140709/virtualbox/box.ovf"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/error/.vagrant.d/boxes/tails-builder-20140709/virtualbox/box.ovf...
OK.
0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: <vbox:Machine> element in OVF contains a medium attachment for the disk image a965b45c-0500-48de-9e31-c7999cdf19fa but the OVF describes no such image
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Appliance, interface IAppliance, callee 
Context: "ImportAppliance" at line 793 of file VBoxManageAppliance.cpp
/usr/share/vagrant/plugins/providers/virtualbox/driver/base.rb:342:in `block in execute'
/usr/lib/ruby/vendor_ruby/vagrant/util/retryable.rb:17:in `retryable'
/usr/share/vagrant/plugins/providers/virtualbox/driver/base.rb:300:in `execute'
/usr/share/vagrant/plugins/providers/virtualbox/driver/version_4_1.rb:172:in `import'
/usr/share/vagrant/plugins/providers/virtualbox/action/import.rb:15:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
/usr/share/vagrant/plugins/providers/virtualbox/action/customize.rb:40:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
/usr/share/vagrant/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:95:in `block in finalize_action'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:69:in `block in run'
/usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:69:in `run'
/usr/lib/ruby/vendor_ruby/vagrant/action/builtin/call.rb:51:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/builtin/config_validate.rb:25:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/builtin/call.rb:57:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
/usr/share/vagrant/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call'
/usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:69:in `block in run'
/usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:69:in `run'
/usr/lib/ruby/vendor_ruby/vagrant/machine.rb:147:in `action'
/usr/lib/ruby/vendor_ruby/vagrant/batch_action.rb:63:in `block (2 levels) in run'
Tasks: TOP => build => vm:up

real    0m1.520s
user    0m1.048s
sys 0m0.144s

I’m sure I’ve done something incorrectly but I’m not able to continue the build at this point.

Attachments

Parent Task: #7527 (closed)

Related issues

Related to #7691 (closed)

Original created by @ioerror on 7661 (Redmine)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information