Tails

#1 Updated by sajolida 2016-08-10 03:39:34

• related to Feature #11627: Consider updating the default system partition's size added

#7 Updated by intrigeri 2017-06-15 06:33:01

• related to Feature #12705: Update the size of the system partition to >= 4 GiB added

#8 Updated by sajolida 2017-08-02 16:07:12

• File upgrade.png added

Here is the dialog we’re talking about.

New version available
=====================

*You should do a manual upgrade to Tails 3.0.*

For more information about this new version, go to https://tails.boum.org/news/version_3.0/

It is not possible to automatically upgrade your device to this new version: there is not enough free space on the Tails system partition.

To learn how to do a manual upgrade, go to https://tails.boum.org/doc/first_steps/upgrade/#manual.

#9 Updated by sajolida 2017-08-02 16:28:50

• Assignee changed from sajolida to intrigeri
• QA Check set to Ready for QA

What about this:

New version available
=====================

*You should do a manual upgrade to Tails 3.0*.

For more information about Tails 3.0, go to https://tails.boum.org/news/version_3.0/.

There is not enough free space on your Tails system partition
to do an automatic upgrade.

Your Tails USB stick (8 GiB):
  * System partition (2.5 GiB): 142 MiB free, 560 MiB required
  * Persistent storage (5.5 GiB): 3.4 GiB free

Manual upgrade instructions: https://tails.boum.org/upgrade/

If there is no persistent storage:

  * No persistent storage (5.5 GiB available)

If the persistent storage is locked:

  * Persistent storage (5.5 GiB, locked)

#10 Updated by intrigeri 2017-08-12 20:48:07

• Status changed from Confirmed to In Progress
• Target version set to Tails_3.2
• % Done changed from 0 to 10

I’ll try to give this a look during this cycle, but I can’t promise I’ll be able to implement the code changes it requires (no idea how hard it’ll be yet).

#11 Updated by intrigeri 2017-08-29 07:54:14

• QA Check deleted (Ready for QA)
• Type of work changed from User interface design to Code

The proposed strings look OK to me. Regarding the code changes required to implement this, at first glance:

• info about the system partition available size seems easy: $no_incremental_reason becomes a hash; when we do $no_incremental_reason = 'not-enough-free-space', we’ll store the additional info no_incremental_explanation will need to build the error message
• info about the needed available space: same as above (we already have access to this info at the time we’ll need to store it in $no_incremental_reason)
• info about the system partition total size: we have no code to do that yet, but I can’t imagine why this would be hard
• info about the persistent storage: this might be more involved. The code we have to identify the persistent volume lives in persistent-setup.git. It uses code from perl5lib.git + a constant from persistent-setup.git, so a little bit of refactoring is needed. Probably no big deal.

Next step is to actually implement this. I’ll try to do it during the 3.2 cycle but I really can’t promise anything.

#12 Updated by intrigeri 2017-09-12 09:29:05

• Target version changed from Tails_3.2 to Tails_3.5

(As kinda expected. The code changes will probably be too invasive for a point release so that won’t be in 3.3.)

#13 Updated by intrigeri 2017-09-12 09:29:21

• Tracker changed from Feature to Bug

#14 Updated by intrigeri 2017-12-23 20:34:01

• related to Bug #14905: Not enough space to auto-upgrade in 10GB .qcow2 virt. hard-drive added

#15 Updated by intrigeri 2017-12-24 11:00:40

• Target version changed from Tails_3.5 to Tails_3.6

intrigeri wrote:
> (As kinda expected. The code changes will probably be too invasive for a point release so that won’t be in 3.3.)

… and 3.5 is going to be a point release as well. Besides, before investing substantial dev time into the Upgrader, I’d rather wait for our sprint on Feature #11679: if we’re going to ditch the Upgrader soonish, I’d rather focus on that instead.

#16 Updated by intrigeri 2018-02-16 09:45:25

• Target version changed from Tails_3.6 to Tails_3.9

One of the nice effects of Feature #15281 is that it will make the problem this ticket is about more rare. More specifically, according to the research anonym did on https://tails.boum.org/blueprint/Endless_upgrades/, with Feature #15281 the problem this ticket is about will remain a thing with 2.5GB system partitions (that we created before Tails 3.2), but it will disappear with 4+ GB system partitions.

So for Tails 3.6 I’ll prioritize fixing the root cause for recently created and future system partitions (via Feature #15281) over working it around for older system partitions via improved UI messages, following the “direct 80% of your resources towards your target userbase that does not use Tails yet, and 20% of them towards your existing users” motto.

Once we’re done on Feature #15281 let’s come back to this and discuss how it should be prioritized vs. other non-budgetted UX improvements we have in mind.

#17 Updated by intrigeri 2018-05-27 07:27:55

• Target version changed from Tails_3.9 to Tails_3.10.1

intrigeri wrote:
> So for Tails 3.6 I’ll prioritize fixing the root cause for recently created and future system partitions (via Feature #15281) over working it around for older system partitions via improved UI messages, following the “direct 80% of your resources towards your target userbase that does not use Tails yet, and 20% of them towards your existing users” motto.
>
> Once we’re done on Feature #15281 let’s come back to this and discuss how it should be prioritized vs. other non-budgetted UX improvements we have in mind.

I’ve done my part of Feature #15281 that got postponed to 3.10. Let’s see where we are on that front in September/October.

#18 Updated by intrigeri 2018-08-20 10:16:37

• related to Feature #14544: Spend software developer time on smallish UX improvements added

#19 Updated by intrigeri 2018-08-20 10:17:23

• Assignee deleted (intrigeri)
• Target version deleted (Tails_3.10.1)

intrigeri wrote:
> intrigeri wrote:
> > Once we’re done on Feature #15281 let’s come back to this and discuss how it should be prioritized vs. other non-budgetted UX improvements we have in mind.
>
> I’ve done my part of Feature #15281 that got postponed to 3.10. Let’s see where we are on that front in September/October.

Feature #15281 is stalled so I’m removing this from my plate until we decide if/when/how we’ll finish implementing it and how to handle Feature #14544.

#20 Updated by intrigeri 2019-01-23 12:54:28

• Status changed from In Progress to Rejected

In favour of Feature #15281.