intrigeri:
> I'm unconvinced (especially given we have to close #5735 first) that
> this can land into 0.22.1, but I'd be glad to see this improved for
> a future iteration. Filed #6575 as a subtask of #6508 (incremental
> upgrades: complete phase four), targetted at Tails 0.23.
Let's do that.
> I've quickly had the code above save the reason why an incremental
> upgrade is not possible. The checks that are done, and the
> corresponding codenames for that reason, are (in chronological order):
>
> 1. non-writable-device
> 2. not-installed-with-tails-installer
> 3. no-incremental-upgrade-path
> 4. not-enough-free-space
> 5. not-enough-free-memory
>
> If one check does not pass, the others are not performed; in practice,
> there might be multiple reasons why an incremental upgrade is not
> possible, but we're only saving one. I think this should be enough to
> substantially improve UX, though.
>
> So, when advising the user to do a manual (full) upgrade, we can now
> insert a sentence that's specific to the primary reason why we cannot
> do an incremental upgrade, e.g.:
>
> 1. "Tails was not started from a writable device."
Which cases does this refer to? when starting from a DVD? a read-only
USB stick? what else?
> 2. "The device Tails is running from was not created using
> Tails Installer."
> 3. "The Tails project does not provide an incremental upgrade to
> this version." (e.g. will be the case for 1.1, most likely)
In the online doc I said:
« No automatic upgrade is available from our website for this version. »
I never used "incremental" in the end.
> 4. "There is not enough free space on the Tails system partition" (a
> bit too technical, but how to express that without having tons of
> people nagging user support because, oh well, they have space
> left on their persistent volume?)
Then, what can I do to get out of this? Reinstall?
> 5. "Not enough memory is available on this system."
