Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 974
    • Issues 974
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 29
    • Merge requests 29
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #7235
Closed
Open
Issue created May 13, 2014 by intrigeri@intrigeriMaintainer

Looser memory requirements when checking for upgrades

Originally created by @intrigeri on #7235 (Redmine)

As documented on #5390 (closed), tails-upgrader-frontend-wrapper’s memory requirements are overly cautious. Without any action from our part, this would force us to implement #5502 in time for Tails 1.1, and be generally bad for users with “only” 1 GiB of RAM, who are already suffering a bit from the current state of things, even on Tails/Squeeze.

Feature Branch: bugfix/looser-memory-requirements-for-upgrades-check

Related issues

  • Related to #5502
  • Related to #5390 (closed)
Edited May 15, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking