Hello nocturo, or anyone else affected, Accepted duplicity into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/duplicity/0.6.18-0ubuntu3.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: duplicity (Ubuntu Precise) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1005901 Title: cannot change temp dir Status in Duplicity - Bandwidth Efficient Encrypted Backup: Fix Released Status in “duplicity” package in Ubuntu: Fix Released Status in “duplicity” source package in Precise: Fix Committed Bug description: SRU justification : Duplicity does not honor the TMPDIR, TEMP, TMP or --tempdir redirection as expected. Impact : If the available size in /tmp is too small, restore may fail to complete Fix : Backport upstream fix applied in 0.6.21 (Merge proposal from the upstream task of this bug) Test Case : Note: Incremental backup is necessary so both the full & difftar are required in /tmp which will require more than 50Mb 1) Mount a 50Mb file system under /tmp ~# df -h /tmp Filesystem Size Used Avail Use% Mounted on /dev/sda1 48M 794K 45M 2% /tmp 2) Create a 60Mb file to be backed up under /srv called data dd if=/proc/kcore of=/srv/data bs=1M count=60 3) Do a full backup of /srv into /backup duplicity full --name test --encrypt-key A6C785C2 --sign-key A6C785C2 --volsize 25 /srv file:///backup/duply 4) Modify the 60Mb file so it can be picked up by the incremental backup dd if=/proc/kcore of=/srv/data bs=1M count=10 conv=notrunc oflag=append 5) Do an incremental backup duplicity incr --name 'duply_test' --encrypt-key A6C785C2 --sign-key A6C785C2 --volsize 25 /srv file:///backup/duply 6) Restore the flag using TMPDIR : TEMPDIR=/mytemp duplicity --name 'duply_test' --encrypt-key A6C785C2 --sign-key A6C785C2 --verbosity '4' --volsize 25 -t now file:///backup/duply /restore With the patch, the command will succeed. Regression : None expected, this code is used in the version currently available in Raring Description of the problem : When /tmp is too small, duplicity is sometimes unable to do a restore. Using TMPDIR variable or --tempdir doe not work. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1005901/+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
