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 944
    • Issues 944
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 13
    • Merge Requests 13
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • tails
  • tails
  • Issues
  • #15557

Closed
Open
Opened 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 admin enable hashed storage. More information
Assignee
Assign to
Tails_3.16
Milestone
Tails_3.16 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: tails/tails#15557