On Sat, Jul 28, 2012 at 2:03 PM, Alexander Zangerl <a...@snafu.priv.at> wrote:
> that's because your filenames contain latin-1 characters. duplicity's log
> module can only work with utf8 or plain ascii. i've reported this issue
> upstream.

Do you have any idea how I could find them? (i.e. outside of duplicity)

> sorry, but that patch isn't just getting rid of the errors but
> removes the logging functionality altogether, without which duplicity
> problems can't be diagnosed properly.

I agree that the patch isn't great however:

1- the logging functionality is not useful in this case since it
breaks before the logging of the offending filenames has a chance to
happen
2- removing the logging means that the rest of the backup can proceed
(if I'm not mistaken)

That's why I thought removing the logging makes sense until the
underlying issue is fixed. Otherwise, duplicity as it stands in wheezy
is broken for me.

Cheers,
Francois


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to