If I do a backup without any carbonfile flags, I see:
Source may have carbonfile support, but support defaults to off.
Use --carbonfile to enable.
If I add a --carbonfile flag, I get:
Error: Bad commandline options: option --carbonfile not recognized
See the rdiff-backup manual page for instructions
Is this expected with v1.1.0, using fink's rdiff-backup-1.1.0-4
package? I looked at the patches in that package, and the only one
that mentions carbonfile doesn't look like it should cause this problem:
# Patch from
# http://savannah.nongnu.org/cgi-bin/viewcvs/rdiff-backup/rdiff-
backup/rdiff_backup/fs_abilities.py.diff?r2=1.21&r1=1.20&diff_format=u
diff -u -r1.20 -r1.21
--- rdiff-backup-1.1.0/rdiff_backup/fs_abilities.py 2005/10/25
06:43:23 1.20
+++ rdiff-backup-1.1.0/rdiff_backup/fs_abilities.py 2005/10/26
00:52:53 1.21
< at > < at > -436,8 +436,8 < at > < at >
self.update_triple(self.src_fsa.carbonfile,
self.dest_fsa.carbonfile,
('carbonfile_active', 'carbonfile_write',
'carbonfile_conn'))
if self.src_fsa.carbonfile and not Globals.carbonfile_active:
- Log("Source may have carbonfile support, but support
defaults to "
- "off.\n Use --carbonfile to enable.", 5)
+ log.Log("Source may have carbonfile support, but support "
+ "defaults to off.\n Use --carbonfile to
enable.", 5)
def set_hardlinks(self):
if Globals.preserve_hardlinks != 0:
Kevin Horton
Ottawa, Canada
