Follow-up Comment #5, bug #13407 (project duplicity):

Hi,

this problem still exists in duplicity-0.5.18. tested against directory
structur created with the perl command in #3

i tried to fix it (without beeing a developer ;)) and ended with this patch.
dont know if it really fixes the problem or if it does harm anything else. but
backup and restore with files copied to the deepest directory which was
created from the perl command works.

please don't use this patch until someone confirms that it does not eat your
cat ;)


--- src/tarfile.py.org  2009-06-08 15:49:54.000000000 +0200
+++ src/tarfile.py      2009-06-20 17:55:49.000000000 +0200
@@ -97,7 +97,7 @@
 #---------------------------------------------------------
 # GNUtar constants
 #---------------------------------------------------------
-BLOCKSIZE  = 512                # length of processing blocks
+BLOCKSIZE  = 1024                # length of processing blocks
 RECORDSIZE = BLOCKSIZE * 20     # length of records
 MAGIC      = "ustar"            # magic tar string
 VERSION    = "00"               # version number
@@ -418,7 +418,7 @@
         buf = "".join(parts)
         chksum = calc_chksum(buf)
         buf = buf[:148] + "%06o " % chksum + buf[155:]
-        buf += (512 - len(buf)) * " "
+        buf += (1024 - len(buf)) * " "
         self.buf = buf
         return buf

@@ -1122,7 +1122,7 @@
         tarinfo.size = len(name)

         return "%s%s%s" % (tarinfo.getheader(), name,
-                           " " * (512 - len(name)))
+                           " " * (1024 - len(name)))

     def _proc_sparse(self, tarinfo):
         """Analyze a GNU sparse header plus extra headers.


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?13407>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/



_______________________________________________
Duplicity-tracker mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/duplicity-tracker

Reply via email to