GPG Error handling

Bug #1730902 reported by Markus
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
Undecided
Unassigned

Bug Description

quite often I do observe this exception with an abort of my backup.

   do_backup(action)
 File "/usr/local/bin/duplicity", line 1515, in do_backup
   check_last_manifest(col_stats) # not needed for full backup
 File "/usr/local/bin/duplicity", line 1217, in check_last_manifest
   last_backup_set.check_manifests()
 File "/usr/local/Cellar/duplicity/0.7.14_1/libexec/lib/python2.7/site-packages/duplicity/collections.py", line 208, in check_manifests
   remote_manifest = self.get_remote_manifest()
 File "/usr/local/Cellar/duplicity/0.7.14_1/libexec/lib/python2.7/site-packages/duplicity/collections.py", line 244, in get_remote_manifest
   (self.remote_manifest_name, str(message)))
UnicodeEncodeError: 'ascii' codec can't encode characters in position 67-68: ordinal not in range(128)

I recommend to use in collections.py, line 244

                    (self.remote_manifest_name, message.encode('ascii', 'ignore')))

rather than str(message)

after changing it this way, my backups are working again

Revision history for this message
Markus (mstoll-de) wrote :

your changes for 0.7.15 do fix this, so you can close this

Now in the error output, I see that the reason was my german localization, causing GPG creating output with UTF 8 characters. It looks to me, at least on other open bug refers to this problem.

Thanks, Markus

Changed in duplicity:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.