** Changed in: deja-dup
Status: Fix Committed => Fix Released
** Also affects: deja-dup (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1159749
Title:
When testing a restore, don't blindly use /tmp
Status in Déjà Dup Backup Tool:
Fix Released
Status in “deja-dup” package in Ubuntu:
New
Bug description:
Fedora and other Linux distributions have started to use a "tmpfs" for
the /tmp/ directory, which has limited space available.
The new cross-distribution rule seems to be: If your application needs
to place large amount of data into a temporary area, then it should
use /var/tmp
The proposal here is to change deja-dup to use /var/tmp
I just ran into this myself, when deja-dup attempted to test a
restore, and storage in /tmp/ was full (deja-dup wrote 3.7 GB).
However, I have to say, I'm a bit surprised by duplicity's strategy.
It attempts to download ALL duplicity-full-signatures files to /tmp,
which in my case, is back to 2011 and has 4.8 GB in total. Why isn't
it sufficient to download only the most recent full signatures file?
Should I file a deparate bug for duplicity?
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1159749/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
