Tails Cloner should enforce correct minimum size if clone Persistent Storage checked
When the "Clone the current Persistent Storage" check button is active the minimum size requirement needs to consider the used space in the Persistent Storage otherwise the cloning might run out of space before completing.
Current Behavior Consequences:
-
When 'Clone the current Persistent Storage' is checked:
- The 'No device suitable' banner shows wrong size required (at least 8.0 GB) if no devices present.
- Target list will be populated with devices that lack enough capacity for the Persistent Storage data.
-
When a target too small for cloning the current Persistent Storage is selected:
- the clone Persistent Storage check button is sensitive and/or can be activated.
- After checking it, Install or Reinstall remain sensitive and can proceed but will fail.
- there is no explanation why cloning the Persistent Storage will fail.
Expected Behavior:
- When 'Clone the current Persistent Storage' is checked:
- repopulate the devices filtered to only show devices large enough to contain a full backup of the currently written Persistent Storage data.
- If no devices are large enough, give the 'No device suitable to backup Tails' banner with the correct minimum size needed.
- verb changes from 'install' to 'backup' similar to !1305 (merged). As devices suitable to install may be found but none for backup.
- Unchecking the button will repopulate the device list based on the installation size only (current behavior).
I'll work on this when my other MRs are reviewed.
Edited by Ben Westgate