On 2012-07-28 at 16:05:59, Alexander Zangerl wrote:
> you mean find files with non-ascii filenames?
> that's easy: find . -regex '.*[^ -~].*'
For some reason that didn't work. I had to use a much more verbose character
class.
So I took a different approach: I replaced the "log.Debug()" calls w
On Sat, 28 Jul 2012 16:40:32 +1200, Francois Marier writes:
>On Sat, Jul 28, 2012 at 2:03 PM, Alexander Zangerl 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
On Sat, Jul 28, 2012 at 2:03 PM, Alexander Zangerl 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)
> so
forwarded 682837 https://bugs.launchpad.net/duplicity/+bug/1030199
tags 682837 - patch
tags 682837 + upstream
thanks
On Thu, 26 Jul 2012 19:15:04 +1200, Francois Marier writes:
>I started seeing these errors every time I do a backup to S3 using duplicity:
>log.Debug(_("File %s is part of known
Package: duplicity
Version: 0.6.18-2
Severity: normal
Tags: patch
I started seeing these errors every time I do a backup to S3 using duplicity:
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1404, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1397, in with_tem
5 matches
Mail list logo
