To be clear, this bug is about filenames that are NOT valid utf8. Most
user errors in bugs and comments here are about filenames that are utf8
-- but not ascii -- and duplicity having problems with that. But this
bug is for those filenames that are truly bizarre.
That said, the fix for both is
Hello,
Not sure if this is the same problem :
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1286845/comments/14
line 130, in copy_file
log.Info(_(Writing %s) % target.get_parse_name())
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 15:
ordinal not in
Hello François,
thanks for your help. I don't have any system-backup.gz neither
examples folder in /usr/share/doc/duplicity/.
So I changed the language of my session (from fr_FR.UTF-8 to
fr_FR.UTF-8) in the system preferences, and now backups are working
again.
Cheers,
Vv
--
You received
Vv: my backup script is a shell script that wraps around duplicity. It's
roughly what can be found in /usr/share/doc/duplicity/examples/system-
backup.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
what exactly do you call your backup script? I launch duplicity with
deja-dup from the unity menu, and I don't see how to specify the locale
this way.
Thanks for your help,
Vv
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Adding only:
export LANG=en_US.utf8
in my backup script works for me. Thanks for the trick.
NB:
I am on precise: duplicity 0.6.18, python 2.7, LANG=fr_FR.UTF-8
This bug does not show when using duplicity on lucid (duplicity 0.6.08b python
2.6, LANG=fr_FR.UTF-8)
--
You received this bug
I can confirm that the work-around in comment 16 does work, although I
had to add this to my backup script:
export LANG=en_US.utf8
export LANGUAGE=
export LC_CTYPE=en_US.utf8
export LC_NUMERIC=en_US.utf8
export LC_TIME=en_US.utf8
export LC_COLLATE=en_US.utf8
export
I've a workaround,
You can change the session language before call to duplicity
declare -x LANG=en_US.UTF-8
It work for me, my default LANG is es_ES.UTF-8, and duplicity fails.
With en_US.UTF-8 works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On a test system I created a folder containing two files:
1. Libreoffice file, created in Ubuntu
2. MS Word file created in Windows
Both foles have Russian names.
I tryed to backup this folder using Deja Dup to UbuntuOne and got same
error.
Then I removed the file from Windows and tryed again,
I need to add that there is no such bug in precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050509
Title:
Duplicity doesn't handle non-utf8 filenames well
To manage notifications about this
Hi guys,
following my non resolved problem (reported on bug 989496 that has been
recently closed), I have tried to remove unicode characters from the
filenames of the photos that I try to backup.
I have checked with convmv (doing a convmv -r -f utf8 -t ascii ./* in
the backed up directory) and
Hello, i have yhis one.
Traceback (most recent call last):
File /usr/bin/duplicity, line 1404, in module
with_tempdir(main)
File /usr/bin/duplicity, line 1397, in with_tempdir
fn()
File /usr/bin/duplicity, line 1248, in main
action = commandline.ProcessCommandLine(sys.argv[1:])
Priority must not be low. I am unable to upgrade just because of this
bug. It affects not onlu non-utf systems, but all systems, where some
files were created in Windows.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, folks,
what a bug!
If I use some other backup space like dropbox folder or gdrive (insync)
I got no such error message. It seems to me a bug in Ubuntu One.
Thanks for help.
BTW: Some of my files were created on Windows.
--
You received this bug notification because you are a member of
Hello François,
thanks for your help. I did remove/add the specified lines.
The previous error is no more, but there is a new one :
Traceback (most recent call last):
File /usr/bin/duplicity, line 1404, in module
with_tempdir(main)
File /usr/bin/duplicity, line 1397, in with_tempdir
Hello François,
I would like to use your patch to be able to resume my backups.
Could you tell me how to do that without breaking my system? Is it
enough to replace the lines with a minus sign at their begining with
the corresponding one with a plus sign in the /usr/lib/python2.7/dist-
Vv: You are correct. To apply the patch, you can simply remove the
lines with minuses and replace them with the lines that start with a
plus.
You can also use the patch -p1 filename.patch command, but given
there's only 3 lines to touch, it might be easier to do it by hand.
--
You received
Here's a version of my patch without the unnecessary print statements.
Again, I'm not pretending to solve the problem, but it may help others
who are waiting for the official fix.
** Patch removed: Hack to work-around the broken debug statements
This is the patch I currently apply every time there's a duplicity
upgrade to work around the broken debug statements and carry on with the
rest of my backup.
It's certainly not ideal an I'm not suggesting it be accepted upstream,
but it may be useful to other users until that bug is fixed.
**
The attachment Hack to work-around the broken debug statements of this
bug report has been identified as being a patch. The ubuntu-reviewers
team has been subscribed to the bug report so that they can review the
patch. In the event that this is in fact not a patch you can resolve
this situation
Coming from bug 989496:
Using Ubuntu One backend, the remote filenames are delivered from
backend.list() are in unicode (json module decodes the utf8 strings into
unicode object). Therefore when copy_to_local(fn) tries to log the data
using log.Notice(_(Copying %s to local cache.) % fn) the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: duplicity (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050509
Title:
Much thanks for taking care of this regression here and in the other
bug! I still think this bug deserves a fix, or at least a better logging
of the problematic file. If for some reason a user ends up with a file
with an invalid name, there's no way of finding out this is the problem
from the GUI,
23 matches
Mail list logo
