Hallo Alexander,

Answers are inside

Danke

Le dimanche 07 mai 2017 à 22:39 +1000, Alexander Zangerl a écrit :
> severity 862005 normal
> tags 862005 + upstream
> forwarded 862005 https://bugs.launchpad.net/duplicity/+bug/1177381
> thanks
> 
> On Sun, 07 May 2017 12:27:57 +0200, Ralf writes:
> > duplicity --no-encryption full --archive-dir
> > /media/userL/backup/log
> > /home/userL file:///media/userL/backup/backup
> 
> just for the record/completeness of the evidence:
> 
> what version of gpg do you have installed?

Package: gnupg
Source: gnupg2
Version: 2.1.18-7 (sid)

> what kind of filesystem is used for /media/userL?

Ext4

> do you have something like tmpreaper installed that might
> delete tempfiles from underneath duplicity?

no

> is this running on a laptop that may have gone to sleep while the
> backup
> was running?

it is a laptop on AC power supply. The crash used to happen within
minutes, no sleep function enabled this way. 

> could you provide the output of a run with -v 9 (anonymised if need
> be)?

I can't reproduce the bug right now, the backup runs fine & is still
running. No failure message within the log file, except the lack of a
dropbox module mentioned at its beginning.

Explanation:
I guessed the bug came from the "--no-encryption" option, which most
systems won't probably use. So I launched before your reply a new try
with the command "duplicity full --archive-dir /media/userL/backup/log
/home/userL file:///media/userL/backup/backup" - initialising the gnupg
passphrase. This way, it worked.

Having received your feedback, I reproduced "duplicity --no-encryption
full --archive-dir /media/userL/backup/log /home/userL
file:///media/userL/backup/backup", 

-> this time it is working fine.

> 
> > Given the simplicity of the command sequence, I am expecting
> > this to be a bug
> 
> upstream's bug tracker has a report that matches your usage
> and error at
> https://bugs.launchpad.net/duplicity/+bug/1177381
> 
> i cannot reproduce the problem here, but upstream seems to be working
> on that particular issue.
> 
> regards
> az
> 
> 

Reply via email to