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 971
    • Issues 971
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • 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
  • #15557
Closed
Open
Issue created Apr 30, 2018 by intrigeri@intrigeriMaintainer

Document workaround for partially applied automatic upgrade

Originally created by @intrigeri on #15557 (Redmine)

As we see on #14754 (closed) sometimes an automated upgrade is partially applied and as a result the upgraded system behaves weirdly. That is occuring a lot recently according to help desk, but I’ve found no way to fix it yet (there’s a tentative fix ready in Git, that will be used first during the 3.9→3.10 upgrade but I’m not counting on it too much).

So IMO we should document a workaround: assuming I’ve upgraded to 3.6.2 and my Tails does not work anymore, I should add a line that contains “3.6.2.squashfs” (without the quotes) at the end of live/Tails.module (at the root of the Tails system partition). Adjust the version number depending on what version one is upgrading to, e.g. if users have the same problem after upgrading to 3.7, they should add a line that contains “3.7.squashfs” instead. Presumably this must be done from a non-Tails system (or from another, working Tails).

Feature Branch: doc/15557-upgrade-to-fix-upgrade

Related issues

  • Related to #10347 (closed)
  • Related to #14754 (closed)
  • Related to #11839 (closed)
  • Blocks #15411 (closed)
  • Blocks #16711 (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