Re: [Duplicity-talk] UnicodeDecodeError

[Alexander Levdonsky]

I agree it was incorrect using. 

But I still'd like to backup more then
one source and so I have one stupid question:
Should I simply use --
allow-source-mismatch option to backup all sources into one
destination?
Or should I copy any source into separate destination?

Thank
s.

On Thu, 2018-03-22 at 20:40 +0000, Aaron wrote:
> Alexander,
> 
> On looking into this in more detail, the easy answer is that it does
> not 
> look as though you are using duplicity correctly and that is causing 
> your problem. You are also hitting a bug around non-ASCII encodings, 
> which you will no longer hit if you fix how you are doing things.
> 
> On 17 March 2018 16:58:15 GMT, Alexander Levdonsky <address@hidden
> ru> 
> wrote (direct to me, I hope you do not mind me posting to the list --
> I 
> have obscured folder names):
> 
>  > It is bash file called with args "full" or "incremental".
>  > It Ubuntu and dirs are inherited from Windows but I believe
> dirnames 
> are utf8 encoded now.
>  > ==
>  > #/bin/bash
>  > /usr/local/bin/duplicity $1 -v 9 --
> tempdir=/media/username/little/tmp 
> --no-encryption ~ file:///media/Archives/Dup
>  > cd /media/username
>  > /usr/local/bin/duplicity $1 -v 9 --tempdir=/media/username/tmp 
> --no-encryption "[Source2]" file:///media/Archives/Dup
>  > /usr/local/bin/duplicity $1 -v 9 --tempdir=/media/username/tmp 
> --no-encryption "[Source3]" file:///media/Archives/Dup
>  > /usr/local/bin/duplicity $1 -v 9 --tempdir=/media/username/tmp 
> --no-encryption "[Source4]" file:///media/Archives/Dup
>  > /usr/local/bin/duplicity $1 -v 9 --tempdir=/media/username/tmp 
> --no-encryption "[Source5]" file:///media/Archives/Dup
>  > ==
> 
> The quick answer is that each of these backup archive targets should
> be 
> different, e.g. "file:///media/Archives/Dup/home", 
> "file:///media/Archives/Dup/Source2" etc.
> 
> Try that and see if it fixes your problem.
> 
> On 18/03/18 06:41, Alexander Levdonsky wrote (direct to me, again I
> hope 
> you do not mind me posting to the list):
> > Well, simple test tree:
> > 
> > Dir "/tmp/test/Dup" as destination
> > Dir "/tmp/test/Name ASCII" as source 1
> > Dir "/tmp/test/Имя UTF8" as source 2
> > Dir "/tmp/test/More ASCII" as source 3
> > 
> > Two full backups are OK, incremental gives the error:
> > /usr/local/bin/duplicity full --no-encryption "Name ASCII" 
> > file:///tmp/test/Dup /usr/local/bin/duplicity full --no-encryption 
> > "Имя UTF8" file:///tmp/test/Dup /usr/local/bin/duplicity
> > incremental 
> > --no-encryption "Name ASCII" file:///tmp/test/Dup
> > 
> > Once again, after cleaning destination, with no UTF8 name:
> > /usr/local/bin/duplicity full --no-encryption "Name ASCII" 
> > file:///tmp/test/Dup /usr/local/bin/duplicity full --no-encryption 
> > "More ASCII" file:///tmp/test/Dup
> > 
> > and finally /usr/local/bin/duplicity incremental --no-encryption
> > "Name 
> > ASCII" file:///tmp/test/Dup
> > Prints correct error message:
> > Fatal Error: Backup source directory has changed. Current
> > directory: 
> > Name ASCII Previous directory: More ASCII
> > 
> > It seems something wrong with storing UTF8 names at manifest?
> 
> Well done, you've found a bug I haven't seen before. I have drilled
> into 
> this and filed it here:
> https://bugs.launchpad.net/duplicity/+bug/1758155
> Please do subscribe to the bug as it would be helpful to have you
> test a 
> fix in the future.
> 
> Many thanks,
> 
> Aaron
>