[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup

2019-04-13 Thread Michael Terry
** No longer affects: deja-dup -- 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/1767122 Title: duplicity Errors 199 at end backup Status in Duplicity: Invalid Status in Python:

[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup

2018-07-08 Thread Kenneth Loafman
** Changed in: duplicity Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned) ** Changed in: duplicity Milestone: 0.7.18 => None -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu.

[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup

2018-06-09 Thread Kenneth Loafman
Yes, read the man page and pay attention to the 'cleanup' and 'remove-*' commands. With $ duplicity cleanup --force " you can clean out any partial backups taking up room. With $ duplicity remove-all-but-n-full 2 you can remove all but the last two backup sets. You should be able to tailor

[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup

2018-06-08 Thread Battant
Hello, I have delete some files from my backup hard drive and I tried again and I have no error So I have this question. 1. On mac os, if your backup drive is full, timeMachie delete the old backups 2. On my mac, if you change the computer name, you can merge tow backup. Questions What's the

[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup

2018-06-07 Thread Kenneth Loafman
Try running it like this from a terminal: $ DEJA_DUP_DEBUG=1 deja-dup &> /tmp/deja-dup.log After it's done, there will be a large log file in /tmp/deja-dup.log. Please look for through it and notice which errors are happening. These were not fatal, just noticeable. NOTE: In another terminal

[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup

2018-06-06 Thread Battant
Hello, I have tried to purge my backup drive and I have try again so I get this error at end backup StartTime 1528282406.66 (Wed Jun 6 12:53:26 2018) EndTime 1528287510.04 (Wed Jun 6 14:18:30 2018) ElapsedTime 5103.38 (1 hour 25 minutes 3.38 seconds) SourceFiles 4084048 SourceFileSize

[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup

2018-06-02 Thread Kenneth Loafman
The log should be in ~/.cache/deja-dup/. If you need more detail, you may need to run "export DEJA_DUP_DEBUG=1" before running deja-dup from the command line. That will produce a detailed log. Look for any errors reported there. I have marked your other bug reports as duplicate of this one.

[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup

2018-05-23 Thread Battant
Helli, Where duplicity.log is stored ? Is log accessible throw journalctl command ? Thanks for your support Best regards Battant -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu.

[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup

2018-05-02 Thread Kenneth Loafman
** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity Status: New => Incomplete ** Changed in: duplicity Importance: Undecided => Medium ** Changed in: duplicity Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman) ** Changed in:

[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup

2018-04-26 Thread Kenneth Loafman
That's saying that duplicity logged 199 errors. They should be present in the log before this summary. It most likely is IO retries, but you should check and let us know what you find. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to

[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup

2018-04-26 Thread Battant
** Also affects: python Importance: Undecided Status: New ** Also affects: deja-dup Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu.