GNOME Bugzilla – Bug 520146
file-roller can not add a .jar to a tar archive
Last modified: 2020-11-11 19:12:14 UTC
Please describe the problem: Received these errors tar: This does not look like a tar archive tar: Error exit delayed from previous errors Steps to reproduce: 1. I have a 1.8 GB folder on an NTFS drive 2. From File Roller, I make a new tar archive and add this folder toit 3. Actual results: fails while part way through addig files with these errors tar: This does not look like a tar archive tar: Error exit delayed from previous errors Expected results: tar from the command line works (as the same user). Does this happen every time? yes Other information:
Created attachment 106573 [details] a file that makes a tar archive in file-roller stop and die I can not add this attached file to a tar via file-roller. Not a permission problem.
I recompiled and turned DEBUG on. The command passed to the shell to add the file to the archive is tar --force-local --no-recursion --no-wildcards -v -p -C /home/tim/Desktop -rf /home/tim/Desktop/testjar.tar -- linkedLists.jar this also fails from the command line. It fails because no archive is created the -r is 'append' I don't know what tar is supposed to do when it gets an append request and there is no archive, but the version that comes with Debian gives an error. Is tar wrong? or should file roller pass -c when adding the first file? the error happens with any file, it is not linked to .jar
maybe be this is related to bug #487012
Paolo, I think you are at least partially correct. I'm confused, but I think that when investigating the problem I encountered, I actually came across two bugs. Bug 1: The first bug is the one I first reported to Debian: that tar was failing while making a tar from a folder of 1.8 GB with many files. The file it was consistently failing on was a .jar. I therefore thought I had a problem adding .jar files to tar using file-roller, and I thought I confirmed that when I found that adding just one .jar to a .tar failed, and I then thought this was tar bug. But I was wrong. tar is happy to add the .jar file if it is invoked like this $ tar -v -cf mydocs.jar mydocs where mydocs is the 1.8GB folder So bug 1 is probably a file-roller bug due to the way it is using tar The fail while adding one file to a not yet existing tar archive is a different bug ... Bug 2: I can't add a single file to a new tar archive because tar complains if it gets -r (append) and there is no archive to append to. This is clearly reported in bug 487012 (http://bugzilla.gnome.org/show_bug.cgi?id=487012). I don't know what the specification of tar is: should -r "append" create an empty file if one does not exist? If the answer is yes, then it's a tar bug. If the answer is "no", then it's a file-roller bug. So that leaves my "bug 1". Comment #14 of bug report 487012 could be related, but the behaviour described in comment 14 seems significantly different from what I see. I see that after adding about 50% of the data, it stops with the same 'command line error' (ie tar exit message) as I see in my "bug 2". I don't get a silent failure. Since it happens after the archive exists, it can't be the same bug as bug 1. Conclusions: 1) the .jar file bug I thought I had was probably a red herring and my bug report is therefore misleading. 2) I think in Debian my bug report could be upgraded to "grave" severity, because file-roller and/or don't seem to be of release quality.
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use file-roller and if you still see this bug / want this feature in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/file-roller/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (volunteer workforce and time is limited).