Bug #9972

Explain better the process when automatic upgrades don't work anymore

Added by BitingBird 2015-08-12 06:14:00 . Updated 2015-11-19 14:45:55 .

Status:
Resolved
Priority:
Normal
Assignee:
emmapeel
Category:
Installation
Target version:
Start date:
2015-08-12
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Upgrader
Deliverable for:

Description

Looks like lots of people arrive to the moment where they can’t automatically upgrade anymore. https://tails.boum.org/doc/first_steps/upgrade/index.en.html#index2h1 gives some explanations, but doesn’t provide step-by-step instructions.

I think it should look like:

1. Manually install a new Tails (link to “manual install from Linux)
2. Boot on the new manually installed Tails
3. Start Tails Installer and use the ”clone and upgrade" option to upgrade the old one, preserving persistence

Subtasks

Related issues

Related to Tails - Bug #10235: Document how to fix a Tails device that got broken for too many automatic updates Resolved 2015-09-23
Is duplicate of Tails - Feature #8874: Assistant: Integrate upgrades Resolved 2015-05-01

History

#1 Updated by sajolida 2015-08-12 10:26:51

This will be covered by the Installation Assistant (see Feature #8874) so I’m tempted to make this as a duplicate or a subtask. Still, if people want to draft something until then why not. I’m personally not going to up a lot of energy into this as I’m solving the problem elsewhere already.

#2 Updated by sajolida 2015-08-12 10:27:11

  • is duplicate of Feature #8874: Assistant: Integrate upgrades added

#3 Updated by BitingBird 2015-08-13 02:44:54

Well, the thing is I had 3 users on irc with the problem yesterday… so I think the next months will be painful for user support if we don’t do something soon. Could I just draft something, and we integrate it without nitpicking, since the page is going to be removed/rewritten completely soon anyway ?

#4 Updated by BitingBird 2015-08-13 02:45:06

  • Assignee set to sajolida
  • QA Check set to Info Needed

#5 Updated by BitingBird 2015-08-13 05:44:34

  • Status changed from New to Rejected

Nervermind.

#6 Updated by sajolida 2015-08-13 14:00:21

Maybe you can have a look and see if what we have already can be improved easily: https://tails.boum.org/doc/first_steps/upgrade#index2h1

#7 Updated by emmapeel 2015-09-23 03:41:27

  • Status changed from Rejected to Confirmed
  • Assignee changed from sajolida to emmapeel

I reopen this bug and take it as part of frontdesk.

I see this problem more and more with each release.

Maybe we can add it to known issues?

#8 Updated by emmapeel 2015-09-23 07:16:08

  • related to Bug #10235: Document how to fix a Tails device that got broken for too many automatic updates added

#9 Updated by sajolida 2015-11-19 14:45:55

  • Status changed from Confirmed to Resolved