Marking Fix Released as this was fixed by rdiff-backup 1.2.0.
** Changed in: rdiff-backup (Ubuntu)
Assignee: Hanno Stock (hefe_bia) (hanno-stock) = (unassigned)
Status: Fix Committed = Fix Released
--
rdiff-backup fails on file with unknown unicode character
Nominated for fixing in Hardy.
I'll look into cherrypicking the fix for Hardy.
I think Intrepid will just get the new upstream version.
** Changed in: rdiff-backup (Ubuntu)
Assignee: (unassigned) = Hanno Stock (hefe_bia) (hanno-stock)
--
rdiff-backup fails on file with unknown unicode
Fix in rdiff-backup CVS -- will be included in rdiff-backup 1.1.17 and
above.
** Changed in: rdiff-backup (Ubuntu)
Status: New = Fix Committed
--
rdiff-backup fails on file with unknown unicode character
https://bugs.launchpad.net/bugs/223280
You received this bug notification because
Hi,
Thank you for reporting this error.
I have corrected the problem in CVS -- rdiff-backup will no longer have
a fatal error if it cannot handle an unknown Unicode character. The fix
will be present in rdiff-backup versions 1.1.17 and above.
Python 3 / 2.6 will introduce much better support
I guess you are referring to The OS configures the setting in a too
late stage during the boot process, only after the NTFS volume was
already mounted., however the volume in question was mounted after
booting via Nautilus.
In any case I think rdiff-backup should handle this more gracefully,
See http://ntfs-3g.org/support.html#locale
--
rdiff-backup fails on file with unknown unicode character
https://bugs.launchpad.net/bugs/223280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: GNU Savannah Bug Tracker #23080
http://savannah.gnu.org/bugs/?23080
** Also affects: rdiff-backup via
http://savannah.gnu.org/bugs/?23080
Importance: Unknown
Status: Unknown
--
rdiff-backup fails on file with unknown unicode character
