Bug #10829

"Tails does not boot after Automatic Upgrade" known issue doc has incorrect cause/consequences analysis

Added by intrigeri 2015-12-31 08:54:39 . Updated 2018-04-08 16:46:36 .

Status:
Resolved
Priority:
Normal
Assignee:
intrigeri
Category:
Target version:
Tails_2.0
Start date:
2015-12-31
Due date:
% Done:

100%

Feature Branch:
emmapeel:bugfix/10829
Type of work:
End-user documentation
Blueprint:

Starter:
1
Affected tool:
Upgrader
Deliverable for:

Description

As said on Bug #10239#note-16:

>> I actually did this weeks ago and told emmapeel about it. From my tests, Tails Upgrader correctly shows the error if < 3 times the IUK’s size of disk space is available.

> OK, so the initial hasty guesses that lead to the branch for Bug #10235 to be merged were wrong, and the documentation that was merged into master is incorrect. anonym, emmapeel, may you please fix this somehow?

Filing as a dedicated ticket because it seems to have been missed.

Subtasks

History

#1 Updated by intrigeri 2015-12-31 08:58:41

  • Assignee set to emmapeel

Emma, do you want to take care of it?

#2 Updated by emmapeel 2016-01-04 13:37:54

  • Status changed from Confirmed to In Progress
  • Assignee deleted (emmapeel)
  • QA Check set to Ready for QA
  • Feature Branch set to emmapeel:bugfix/10829
  • Starter set to Yes

Sure! I didnt saw it.

Please review branch at emmapeel:bugfix/10829

#3 Updated by intrigeri 2016-01-04 13:51:36

  • Assignee set to intrigeri
  • Target version set to Tails_2.0

Thanks!

#4 Updated by intrigeri 2016-01-05 19:46:35

  • Assignee changed from intrigeri to emmapeel
  • % Done changed from 0 to 50
  • QA Check changed from Ready for QA to Dev Needed
  • Feature Branch deleted (emmapeel:bugfix/10829)

The proposed branch adds dozens of *.es.po, so I cherry-picked the relevant commit only. Thanks!

The only reason I’m not closing this ticket is that the “Automatic Upgrade” spelling seems to be unique to this known issue. Maybe make it consistent with the rest of our doc?

#5 Updated by emmapeel 2016-01-06 08:03:23

  • Feature Branch set to emmapeel:bugfix/10829

Ok, I think now it looks like in the rest of the website. I also added a little application span. Please review.

#6 Updated by emmapeel 2016-01-06 08:04:05

  • Assignee deleted (emmapeel)
  • QA Check changed from Dev Needed to Ready for QA

#7 Updated by intrigeri 2016-01-06 11:18:12

  • Assignee set to emmapeel
  • QA Check changed from Ready for QA to Info Needed

> Ok, I think now it looks like in the rest of the website.

Well, I have my doubts: looks like we write it “automatic upgrade” everywhere, except when we have specific reason to capitalize “Automatic”, like at the beginning of a sentence. Did I miss anything?

> I also added a little application span.

I’m surprised by <span class="application">Tails</span>. Do we really treat “Tails” as an application name anywhere else in our doc? I could not find any examples.

#8 Updated by emmapeel 2016-01-06 11:31:16

  • Assignee changed from emmapeel to intrigeri
  • QA Check changed from Info Needed to Ready for QA

Ok, I agree. I think I needed to separate automatic upgrade from Tails. I added some colons now.

What do you think? (assigning to you because of previous review)

#9 Updated by emmapeel 2016-01-06 11:38:17

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

Applied in changeset commit:74f13b02d08dfbb90440514e2e0b2bb7bd1188f9.

#10 Updated by intrigeri 2016-01-06 11:38:29

> What do you think?

I love it! Merged, thank you :)

#11 Updated by intrigeri 2018-04-08 16:46:36

  • QA Check deleted (Ready for QA)