That more recent error (the one with Backup Statistics in its crash
report) is bug 1286845.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989496
Title:
UnicodeDecodeError during backup due to
deja-dup_30.0-0ubuntu4 (trusty)
duplicity_0.6.23-1ubuntu2 (trusty)
Traceback (most recent call last):
File /usr/bin/duplicity, line 1493, in module
with_tempdir(main)
File /usr/bin/duplicity, line 1487, in with_tempdir
fn()
File /usr/bin/duplicity, line 1336, in main
** Changed in: duplicity
Milestone: None = 0.6.23
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989496
Title:
UnicodeDecodeError during backup due to non-utf8 translation
To manage
** Changed in: duplicity
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989496
Title:
UnicodeDecodeError during backup due to non-utf8 translation
To manage
Woops, I wrote my remarks in the middle of the log. The previous comment
should have started with:
When doing a different backup to an external drive, I got an error which was
not present before:
duplicity incremental ~/ -v Info --exclude ~/... [skipped]
file:///run/media/milan/SOMETHING
Utilisation du répertoire d’archive :
/home/milan/.cache/duplicity/e5f4f9b85e256f59787be25a63b7fdbf
Utilisation du nom de sauvegarde : e5f4f9b85e256f59787be25a63b7fdbf
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
Import
...and when passing a path with spaces, like file:///run/media/milan/TOSHIBA\
EXT/, I get:
Command line error : Expected 2 args, got 3
Looks like the path is split into two arguments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Great, now it works -- at least it fixes the crash I fixed with my quick
patch (and most probably much better).
(Sorry for missing the relevant gettext lines in the commit.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hey, thanks for working on this! ;-)
Unfortunately, with your branch I get a crash directly on start (FWIW, I've
only built duplicity in-tree, and not installed it).
$ bin/duplicity --help
Traceback (most recent call last):
File bin/duplicity, line 1470, in module
with_tempdir(main)
File
Milan, thanks for testing! I've updated the branch to fix that issue.
Can you try again?
You'll see that I do fix the gettext.install() line in
duplicity/__init__.py, but slightly differently than you suggest (I
avoid using the names= argument, because that only appeared in python
2.5; but I
For those experiencing the 'ascii code can't encode character' issue,
I'm curious if lp:~mterry/duplicity/encoding solves the problem for you.
Please report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think I have found a fix.
The bug does not happen only with invalid UTF-8 filenames, you simply
need UTF-8 filenames and a UTF-8 locale.
For example, in collections.py:810, there is:
log.Debug(_(File %s is not part of a known set; creating new
set) % (filename,))
On my
I also get this error doing a backup to webdav
Filenames have not strange characters in names (although my LOCALE is
es_ES.UTF-8)
Traceback (most recent call last):
File /usr/bin/duplicity, line 1411, in module
with_tempdir(main)
File /usr/bin/duplicity, line 1404, in with_tempdir
I changed the line (/usr/lib/python2.7/dist-
packages/duplicity/collections.py):
log.Debug(_(Ignoring file (rejected by backup set)
'%s') % filename)
to this:
print Ignoring file (rejected by backup set, filename
and backups now work perfect!
So It
deja-dup 24.0 is still affected by this broblem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989496
Title:
UnicodeDecodeError during backup due to non-utf8 translation
To manage notifications
0.6.20-2 is still affected by this problem, at least using the
fr_CA.utf8 locale.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989496
Title:
UnicodeDecodeError during backup due to non-utf8
i've dug into this a bit more deeply and found an explanation for the
logging gotchas under certain locales:
as per the python wiki
(http://web.archive.org/web/20120425192131/http://wiki.python.org/moin/UnicodeEncodeError)
when you run somestring.decode(whicheverencoding) python2 does weird
I'm runnin ubuntu 12.04 with duplicity 0.6.20(but had same error with duplicity
0.6.18 and 0.6.19) and had same problem. I do backups on webdav.
duplicity --include-globbing-filelist /etc/backup-files.txt /
webdavs://login:p...@webdav.yandex.ru/Bakeups/nightserv/
Чтение подстановочного списка
Oleg, you may be talking about bug 1080423.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989496
Title:
UnicodeDecodeError during backup due to non-utf8 translation
To manage notifications about
Michael, there is a difference, I use webdav instead ubuntu one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989496
Title:
UnicodeDecodeError during backup due to non-utf8 translation
To manage
For those of you using Ubuntu One and still experiencing this error, see
bug 1080423. It's a bug in duplicity's Ubuntu One backend where it
returns unicode instead of utf8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: hundredpapercuts
Status: Triaged = Fix Released
** Changed in: duplicity
Status: Fix Committed = Fix Released
** Changed in: duplicity (Ubuntu)
Status: Triaged = Fix Released
** Changed in: hundredpapercuts
Milestone: raring-misc = None
--
You received
According to comment #30 this bug is fixed. The remaining issues are
being tracked in bug #1050509
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989496
Title:
UnicodeDecodeError during backup due
How about inform the offending filename in the error message until a
suitable fix is written?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989496
Title:
UnicodeDecodeError during backup due to
** Changed in: hundredpapercuts
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989496
Title:
UnicodeDecodeError during backup due to non-utf8 translation
To
Hello,
this is still not working for me after upgrading to 12.10 and Deja-dup
24.0. I got the same error message as with the previous versions :
Traceback (most recent call last):
File /usr/bin/duplicity, line 1404, in module
with_tempdir(main)
File /usr/bin/duplicity, line 1397, in
** Changed in: hundredpapercuts
Milestone: None = raring-misc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989496
Title:
UnicodeDecodeError during backup due to non-utf8 translation
To manage
Ok, I have been using Deja-dup and not duplicity directly, and my Ubuntu
backup routine was working before this bug appeared, and was broken. I
updated yesterday, and this is now fixed for me. My backup just finished
successfully, and i'm happy.
--
You received this bug notification because you
It looks like the fix is incomplete.
Russian locale, UTF-8 causes basically the same error here:
log.Notice(_(Copying %s to local cache.) % fn)
fn is a unicode string while _(Copying %s to local cache.) returns a
str with utf-8 contents. And the value of fn is a unicode string causing
the
Roman, if a filename isn't in utf8, that's bug 1050509. Can you repeat
your comment there, and explain how you got unicode filenames? Your
filesystem locale is utf16?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is fixed now, so marking done for hundredpapercuts.
** Changed in: hundredpapercuts
Status: Confirmed = Fix Released
** Changed in: duplicity (Ubuntu)
Assignee: Michael Terry (mterry) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
31 matches
Mail list logo
