Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
T
tails
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 967
    • Issues 967
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 22
    • Merge Requests 22
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #7134

Closed
Open
Opened Apr 28, 2014 by anonym@anonymMaintainer

Fix Vagrant compatibility issue: cannot build after vm:up

Originally created by @anonym on #7134 (Redmine)

Taken from: https://mailman.boum.org/pipermail/tails-dev/2014-April/005574.html

This branch’s main purpose is to fix a compatibility issue between “old”
and “new” Vagrant reported on tails-dev@ a while ago [1] that prevents
doing something like:

rake vm:up
rake build

The ‘build’ task doesn’t work if issued when the VM is already up,
because of VM API changes, so a “compabitility layer” is needed.
However, it works when a `build` is issued when the VM is not up.
Since the code that fails in the former case is the cpu and memory
checks, it suggests that they are not done in the latter, which is
wrong. This branch also fixes that, so the checks are always performed,
no matter the VM state.

[1] https://mailman.boum.org/pipermail/tails-dev/2014-February/005042.html

Feature Branch: bugfix/fix-vagrant-compatibility-issues

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tails_1.1
Milestone
Tails_1.1 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: tails/tails#7134