Bug #6736

Handle new Vagrant base boxes gracefully

Added by anonym 2014-02-20 02:01:16 . Updated 2014-09-02 05:17:30 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Build system
Target version:
Start date:
2014-02-20
Due date:
% Done:

100%

Feature Branch:
feature/vagrant-wheezy-basebox
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

If there’s a new Vagrant base box for building Tails (like we had around Dec 23 2013, as shown by the new checksum in commit 89f8b20) there’s currently no mechanism to detect and deal with this. Users are left with a Vagrant setup based on the old base box without being informed of this, and will experience whatever issue that was the reason for updating the base box.

It’s demonstrated quite nicely by the current workaround user’s have to go through to rid themselves of the old stuff:

cd path/to/tails-sources/vagrant
# Delete the outdated vagrant machine
vagrant destroy -f
# Delete the cached, old base box so we'll download the new
# one that unfortunately is named the same...
vagrant box remove tails

One unfortunate thing is that there’s no notion of version for our base box currently. The actual base box file is named squeeze.box (always the same — only the checksum differs, but that doesn’t deal with the cache), and we don’t give an internal name (in Vagrant) so it’ll just be called default. We probably want to add a version number (perhaps we can use the creation date?) to both of these. This version should then be included in the Tails sources, indicating what is up-to-date. We’ll then compare these to automate something like the above workaround.

While we’re at it we can also switch the name from “squeeze” to “tails-builder” or something more descriptive.


Subtasks


Related issues

Related to Tails - Bug #7218: Update Vagrant basebox to Wheezy Resolved 2014-05-11
Has duplicate Tails - Bug #6730: Vagrant build broken on Wheezy Duplicate 2014-02-19
Blocked by Tails - Bug #7643: Vagrant 1.4.3 (from sid) needed on Wheezy Resolved 2014-07-22

History

#1 Updated by anonym 2014-07-10 01:41:29

  • has duplicate Bug #6730: Vagrant build broken on Wheezy added

#2 Updated by anonym 2014-07-10 21:15:19

  • Status changed from Confirmed to In Progress
  • Assignee deleted (anonym)
  • Target version set to Tails_1.1
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA
  • Feature Branch set to feature/vagrant-wheezy-basebox

#3 Updated by anonym 2014-07-10 23:01:36

  • Assignee set to intrigeri

#4 Updated by intrigeri 2014-07-13 08:42:15

  • Assignee changed from intrigeri to anonym
  • QA Check changed from Ready for QA to Dev Needed

#5 Updated by intrigeri 2014-07-19 19:06:05

  • related to Bug #7218: Update Vagrant basebox to Wheezy added

#6 Updated by intrigeri 2014-07-20 19:58:46

  • Target version changed from Tails_1.1 to Tails_1.1.1

#7 Updated by anonym 2014-07-20 20:09:08

  • Assignee changed from anonym to intrigeri
  • QA Check changed from Dev Needed to Ready for QA

#8 Updated by intrigeri 2014-07-22 19:20:12

  • blocked by Bug #7644: This branch's box.ovf file has a very small mistake added

#9 Updated by intrigeri 2014-07-22 19:22:46

  • blocked by Bug #7643: Vagrant 1.4.3 (from sid) needed on Wheezy added

#10 Updated by intrigeri 2014-07-25 09:01:28

  • blocks deleted (Bug #7644: This branch's box.ovf file has a very small mistake)

#11 Updated by intrigeri 2014-07-25 09:02:30

  • Status changed from In Progress to Fix committed
  • Assignee deleted (intrigeri)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

#12 Updated by anonym 2014-09-02 05:17:30

  • Status changed from Fix committed to Resolved