** Changed in: duplicity
Status: In Progress => Fix Released
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Changed in: duplicity
Milestone: 0.8.01 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1177381
Title:
Duplicity can't find its own tempdir
To manage notifications about this bug go to
** Changed in: duplicity
Milestone: 0.8.00 => 0.8.01
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1177381
Title:
Duplicity can't find its own tempdir
To manage notifications about this bug go
I guess I have a related error.
Initially I used deja-dup for the backup on ubuntu 17.10, but it fails silently
since weeks.
So I manually launched duplicity to find what is the error and it is quite
cryptic :
PASSPHRASE= duplicity incremental --progress --full-if-older-
than 90D --exclude --e
If I restart the backup it has not completed:
$ duplicity --no-encryption /home/ file:///
Local and Remote metadata are synchronized, no sync needed.
Last full backup left a partial set, restarting.
Last full backup date: Thu Mar 30 13:08:19 2017
RESTART: Volumes 6223 to 6223 failed to upload befor
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1532, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1526, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1380, in main
do_backup(action)
File "/usr/bin/duplicity", line 1501, in do_backup
full_
** Changed in: duplicity
Milestone: None => 0.7.11
** Changed in: duplicity
Milestone: 0.7.11 => 0.8.00
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Status: New => In Progress
** Changed in: duplicity
Assignee: (unassigned) => Kenneth
@Michael, I'm looking as well. My gut says that something got threaded and
we're not joining at the end of the run, but I cannot find any indication
of that at all.
On Wed, Dec 14, 2016 at 5:48 PM, Karl <1177...@bugs.launchpad.net> wrote:
> I'm using a laptop with my power settings set to "Do n
I'm using a laptop with my power settings set to "Do nothing" when the lid is
closed. However, I can replicate this by starting duplicity, waiting for it to
get going, then closing my laptop lid.
I think Ubuntu is cleaning the temp files out from under Duplicity?
I'm using Ubuntu 16.10 (so gpg
I'm having a hard time figuring out why this would happen just from
examining the code. If someone knows a way to reproduce this, that
would be a huge help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Bug 922101 might be related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1177381
Title:
Duplicity can't find its own tempdir
To manage notifications about this bug go to:
https://bugs.launchpad.n
11 matches
Mail list logo
