Feature #9889
Decide a backup solution among possible candidates
0%
Description
Subtasks
Related issues
Blocked by Tails - |
Resolved | 2015-08-03 | |
Blocked by Tails - |
Resolved | 2015-01-27 | |
Blocked by Tails - |
Resolved | 2015-09-01 |
History
#2 Updated by sajolida 2015-08-10 05:48:00
- Parent task set to Feature #7049
#3 Updated by intrigeri 2015-08-28 01:52:01
- Blueprint set to https://tails.boum.org/blueprint/backups
#4 Updated by intrigeri 2015-08-28 01:53:36
- Subject changed from Decide a backup solution amongst possible candidates to Decide a backup solution among possible candidates
#5 Updated by sajolida 2015-08-28 07:42:56
- blocked by
Bug #9888: Test deja-dup to do backups added
#6 Updated by sajolida 2015-08-28 07:43:39
- blocked by
Feature #8812: Consider using Tails Installer to do backups added
#7 Updated by sajolida 2015-08-28 07:43:55
- Type of work changed from Discuss to Wait
That’s not ready for discussion yet. Adding blockers and changing type of work accordingly.
#8 Updated by sajolida 2015-09-21 03:19:26
- Target version set to 2016
#9 Updated by sajolida 2016-07-01 11:28:59
- blocked by
Bug #10145: Investigate issues related to permissions for backup system added
#10 Updated by sajolida 2016-07-01 11:29:45
Seeing Bug #9888#note-18 it seems like we have to choose between improving and adapting deja-dup or designing a custom GUI. This is still blocked by more research to be done.
#11 Updated by sajolida 2016-07-01 11:32:00
Using Tails Installer (Feature #8812) could be considered as a third alternative as the GUI would be minimal and orders of magnitude simplier than if we want to write our own GUI on top of whatever backend we prefer.
#12 Updated by intrigeri 2016-07-01 18:59:10
> Using Tails Installer (Feature #8812) could be considered as a third alternative as the GUI would be minimal and orders of magnitude simplier than if we want to write our own GUI on top of whatever backend we prefer.
I’m probably misunderstanding what you mean with “orders of magnitude simplier”, so you might want to clarify (if/whenever you feel it’s worth it).
#13 Updated by intrigeri 2016-08-27 10:11:31
- Target version deleted (
2016)
(Let’s only keep the parent ticket on the roadmap, for clarity’s sake.)
#14 Updated by sajolida 2018-06-04 12:46:50
- Target version set to Tails_3.8
#15 Updated by sajolida 2018-06-25 15:47:33
- Target version changed from Tails_3.8 to Tails_3.9
- Type of work changed from Wait to Research
Tails Installer is being deprecated so I don’t think it’s the way forward either.
I’ve now tested every possible graphical backup application for Linux, inside and outside Debian and I don’t think that any existing interface would work for us, especially given the complex permissions setting of Tails.
I’m quite convinced now that writing our own interface, well integrated in Tails, is the way forward. But we could rely on existing backends.
Next I’ll write a comparison of backends but I won’t investigate graphical interfaces further myself.
#16 Updated by intrigeri 2018-09-05 16:26:47
- Target version changed from Tails_3.9 to Tails_3.10.1
#17 Updated by sajolida 2018-10-21 20:44:29
- Target version deleted (
Tails_3.10.1)
I’ll work again on this once we have resources for the implementation.
#18 Updated by sajolida 2019-07-23 16:25:51
- Status changed from Confirmed to Rejected
- Assignee deleted (
sajolida)
I updated the blueprint with my latest plans. I don’t think that we can choose “a backup solution among possible candidates” so I’ll reject this ticket.
But feel free to reopen it and prove me wrong!