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 similar. Ever since adding gettext support, we've used utility functions in util.py to convert between byte and unicode strings. Those functions pass the 'replace' option to decode/encode while they're at it, which gracefully handles non-utf8 characters. As we fix normal utf8 conversion errors, by using those utility functions we also make the non-utf8 cases better. So where are we today? We've fixed a bunch of UnicodeDecodeErrors throughout duplicity [1]. I don't think we've fixed 100% of them, but I do think we've hit the majority of the use cases by now. This generic bug might not be super useful anymore. It might be better to close this? And keep using separate bugs for each specific instance of a decode error. [1] https://bugs.launchpad.net/duplicity/+bugs?field.searchtext=ordinal+not+in+range&orderby=-status&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1050509 Title: Duplicity doesn't handle non-utf8 filenames well Status in duplicity package in Ubuntu: Confirmed Bug description: This is a break-out bug from bug 989496. If the user is using a filename encoding that is non-utf8, duplicity doesn't have special support for that. It mixes use of filenames for both printing/logging and for opening. All print/log uses should use a utf8 version of the filename. All actual file operations should use the native encoding. This will likely involve a new field like pretty_name or something on ROPath. I suspect the number of users with non-utf8 systems is low. So I'm setting as low priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1050509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
