rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] TypeError: unsubscriptable object (cfile['creat


From: Kevin Horton
Subject: Re: [rdiff-backup-users] TypeError: unsubscriptable object (cfile['creator'])
Date: Sun, 16 Oct 2005 08:45:06 -0400

On 15 Oct 2005, at 22:49, Ben Escoto wrote:

Kevin Horton <address@hidden>
wrote the following on Fri, 14 Oct 2005 23:16:18 -0400


It seems that with OS X 10.4 you need to use two switches:

--no-carbonfile --override-chars-to-quote ''

The second switch ends with two single quote characters.  It might
only be necessary if you are backing up to and from the native HFS+
file system.


What if you add this patch:

--- rpath.py    2005-09-07 12:04:37.000000000 -0500
+++ rpath.py.new        2005-10-15 21:48:04.000000000 -0500
@@ -1150,6 +1150,7 @@

        def write_carbonfile(self, cfile):
                """Write new carbon data to self."""
+               if not cfile: return
log.Log("Writing carbon data to %s" % (self.index,), 7)
                from Carbon.File import FSSpec
                import MacOS

Do you still need to add --no-carbonfile, or does that fix that
problem?

This patch seems to stop the crash. I did an incremental backup, and now I get a bunch of UpdateErrors like this:

UpdateError Desktop/RV_Stuff/POH archive/graphs/all-3.gp Updated mirror temp file /Volumes/Ext_BU/Users/kwh/rdiffbu/Desktop/RV_Stuff/ POH archive/graphs/rdiff-backup.tmp.7305 does not match source

The file listed in the first of these UpdateErrors was the one that was causing the crash before I started using the --no-carbonfile flag. I assume the backed up file would have included the carbonfile data if that flag had not been used, and this is why rdiff-backup is now complaining about the file not matching the source. Does this make sense?


Kevin Horton
Ottawa, Canada






reply via email to

[Prev in Thread] Current Thread [Next in Thread]