Bug saving changes to files stored in tar archives

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • adlan
    Visitor
    • Aug 2011
    • 7

    Bug saving changes to files stored in tar archives

    Hi,
    Beyond Compare (Version 4.0 (build 18847)) is working well to compare two tar archives (created with tar (GNU tar) 1.27.1) - it identifies the different files and orphans correctly, and is correctly able to read the files inside the tar archive to perform a comparison.

    However, I think there is a bug when I attempt to save changes back into one of the tar archives. The file that has been modified is replaced with an empty folder.
    To reproduce.
    1. Compare two tar archives using Folder compare.
    2. Double click one of the text files inside the tar file to compare the contents.
    3. make changes to the text file you are comparing.
    4. save changes
    5. Close text file comparison and refresh folder compare.
    6. File that was saved is now shown as being 0 bytes in size.

    If I do a contents listing of the modified tar file, the text file is now listed as a directory.

    Regards
    Andrew.
    Last edited by adlan; 25-Oct-2014, 09:51 PM.
  • Aaron
    Team Scooter
    • Oct 2007
    • 15997

    #2
    Thanks for the bug report. There does seem to be a write issue with our Tar support. I'll open a bug tracker entry to get this fixed.
    Aaron P Scooter Software

    Comment

    • adlan
      Visitor
      • Aug 2011
      • 7

      #3
      Thanks Aaron, I'll look out for the fix. Also thanks for moving my post to the correct thread, I didn't notice the folder compare section was for BC 3 until after I posted and I couldn't work out how to move it to the correct location afterwards.

      Comment

      • Chris
        Team Scooter
        • Oct 2007
        • 5538

        #4
        This should be fixed in Beyond Compare 4.0.1 that we released today.
        Chris K Scooter Software

        Comment

        • adlan
          Visitor
          • Aug 2011
          • 7

          #5
          Thanks Chris,
          I tested 4.0.2 and I agree that the problem is fixed.
          Cheers
          Andrew.

          Comment

          Working...