On 02/22/2016 07:02 AM, intrigeri wrote:
> Hi,
>
> anonym just merged the branch for #9262 aka. "Port our ISO build
> system to Jessie", so if you have an ISO build setup, you need to
> upgrade it:
>
> * manual build system
>
> See the updated doc: https://tails.boum.org/contribute/build/#manual
>
> * Vagrant (untested)
>
> rake vm:destroy
> rm -r vagrant/.vagrant
> rake vm:up
>
> Please report any issues to us :)
>
> JFTR, our Jenkins ISO builders have been upgraded yesterday already.
>
> Cheers,
It broke vagrant for me:
austin@debian-laptop:~/src/tails$ time rake build
Using HTTP proxy:
http://tails-builder-20150609.vagrantup.com:3142
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-20150609' 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-20150609.box
Extracting box...te: 687k/s, Estimated time remaining: 0:00:01))
Successfully added box 'tails-builder-20150609' with provider 'virtualbox'!
[default] Importing base box 'tails-builder-20150609'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Running 'pre-boot' VM customizations...
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
rake aborted!
Vagrant::Errors::VMBootTimeout: Timed out while waiting for the machine
to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period. This can
mean a number of things.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout")
value./usr/share/vagrant/plugins/providers/virtualbox/action/customize.rb:40:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/boot.rb:18:in `call'
/usr/share/vagrant/plugins/providers/virtualbox/action/customize.rb:40:in `call'
/usr/share/vagrant/plugins/providers/virtualbox/action/sane_defaults.rb:49:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/forward_ports.rb:31:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/network.rb:112:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/clear_network_interfaces.rb:26:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/prepare_nfs_settings.rb:15:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/prepare_nfs_valid_ids.rb:12:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:13:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/set_name.rb:48:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/check_accessible.rb:18:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in
`call'
/usr/share/vagrant/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in
`call'
Tasks: TOP => build => vm:up
there was a similar issue happening before, that required ssh'ing into
builder and updating grub. This time, it's udev, and I can't force it to
upgrade:
Unpacking udev (215-17+deb8u3) over (215-17+deb8u1) ...
dpkg: error processing archive
/var/cache/apt/archives/udev_215-17+deb8u3_amd64.deb (--unpack):
trying to overwrite `/lib/udev/write_net_rules', which is the diverted
version of `/lib/udev/write_net_rules.udev'
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for systemd (215-17+deb8u1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Errors were encountered while processing:
/var/cache/apt/archives/udev_215-17+deb8u3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
removing the divert gets it further:
# dpkg-divert --remove /lib/udev/write_net_rules.udev
# apt-get -f install
doing an apt-get upgrade then pops up a curses dialog for grub device
install. Finishing that, and dist-upgrade works. Trying to run:
$ rake build
fails, with:
sudo: /vagrant/provision/setup-tails-builder: command not found
Not sure where to go from there
