first of all: 7-Zip treats such files as they are => at gzipped tar-file. That means you should get a tar-file when you extract the above mentioned file. This tar-file has to be unpacked further. (at least this should be true for the first mentioned file).
second: have you tried right-clicking on that file and choosing "Extract to jruby-bin-1.5.1.tar"? This should create a folder named "jruby-bin-1.5.1.tar" in which the file "jruby-bin-1.5.1.tar" resides. This can be unpacked just the way as before -> right-click and choose any entry from the context-menu of 7-Zip you prefer.
Please give feedback here.
Best regards!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With many other *.tar.gz and *.tgz files I'm able to keep double-clicking in the GUI to open up the tar file contents. I'm not able to do that with 9.15 on the example files. Things break once I try to double-click on the tar file icon in the file manager GUI.
Also, while I'm able to extract the jruby-bin-1.5.1.tar file via the GUI into a folder, I get the same error when opening up the tar file by double-clicking on it.
I'm able to untar from a MSYS shell (gnu tar v1.23) using "tar -tvf jruby-bin-151.tar" so everything still points to something not quite right in the 7-Zip code.
As I said, this error doesn't happen with all gzipped tar files. I'm currently only having problems with the ones mentioned.
Jon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm having the same issue with .tar files from our in house HP-UX 11i servers, since upgrading to 9.15 (beta) from 4.62.
The same file opened fine in the older version but now it does not.
I believe that this is definitely a bug in 9.15 (beta) and needs investigating.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Strangely, basic-bsdtar (static linked against liblzma 4.999beta9??) works like a champ with both the previously mentioned jruby and scala gzipped tar files.
As much as I'm a fan of 7-zip I still think there's a bug lurking in 9.15's handling of tars.
"scala-2.8.0.final-devel-docs(2).tar":
junk after hex offset 7c22600
and, for example, two copies of scala-2.8.0.final-devel-docs/tools/scalap.html.
Second copy in junk block.
"jruby-bin-1.5.1(2).tar" same problem:
junk after hex offset 2771200
So just ask authors of these files why they use incorrect TAR software.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So 7-zip 9.15 is better:
1) It extracts good TAR archives.
2) It shows that some TAR archives are "bad". So users can ask developers of "bad" software to fix bugs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-09-08
Hello !
I have exactly the same problem with 7zip 9.15 and 9.16 on other tar files ; for instance, those coming from SF project "Java Service Wrapper".
I went back to 7zip 4.65 because of this…
I think it will be a problem to ask all developers over the world to fix their tar archives ;-)
Best regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We must ask developers about version of TAR software that was used to create these "bad" archives.
And then we can ask these TAR software developers to fix bugs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can I ask where are you getting your tar file format definition from? Can you post a link to it here please.
Every other tar program that I've used will open my tar files perfectly fine except for 7-zip 9.15 and later.
Are saying that it's the fault of every other tar file manufacturer except yourself? If so please show us the proof.
7-zip is a great application, and we all appreciate the hard work and effort that you've put in over the years, but this broken tar file support is getting beyond a joke.
Please please please either fix it, or give us the option to support so called "broken" tar files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On either Win7 or WinXP using the GUI (haven't tried 7za.exe yet) I can't extract the following
http://jruby.org.s3.amazonaws.com/downloads/1.5.1/jruby-bin-1.5.1.tar.gz
http://www.scala-lang.org/downloads/distrib/files/scala-2.8.0.final-devel-docs.tgz
and get an error dialog (on Win7) when trying JRuby stating
Can not open 'C:\Users\Jon\AppData\Local\Temp\7zO168.tmp\jruby-bin-1.5.1.tar' as archive
Can anyone replicate, or provide suggestions if this turns out to be my system issue?
Jon
Hello everyone,
first of all: 7-Zip treats such files as they are => at gzipped tar-file. That means you should get a tar-file when you extract the above mentioned file. This tar-file has to be unpacked further. (at least this should be true for the first mentioned file).
second: have you tried right-clicking on that file and choosing "Extract to jruby-bin-1.5.1.tar"? This should create a folder named "jruby-bin-1.5.1.tar" in which the file "jruby-bin-1.5.1.tar" resides. This can be unpacked just the way as before -> right-click and choose any entry from the context-menu of 7-Zip you prefer.
Please give feedback here.
Best regards!
With many other *.tar.gz and *.tgz files I'm able to keep double-clicking in the GUI to open up the tar file contents. I'm not able to do that with 9.15 on the example files. Things break once I try to double-click on the tar file icon in the file manager GUI.
Also, while I'm able to extract the jruby-bin-1.5.1.tar file via the GUI into a folder, I get the same error when opening up the tar file by double-clicking on it.
I'm able to untar from a MSYS shell (gnu tar v1.23) using "tar -tvf jruby-bin-151.tar" so everything still points to something not quite right in the 7-Zip code.
As I said, this error doesn't happen with all gzipped tar files. I'm currently only having problems with the ones mentioned.
Jon
Has anyone been able to confirm that this behavior is a bug in 7-Zip?
Is there a more appropriate place (like the Tracker) that this issue should be listed?
Jon
scala-2.8.0.final-devel-docs.tar
probably is corrupted:
there is some junk at the end of archive.
I'm having the same issue with .tar files from our in house HP-UX 11i servers, since upgrading to 9.15 (beta) from 4.62.
The same file opened fine in the older version but now it does not.
I believe that this is definitely a bug in 9.15 (beta) and needs investigating.
Old version of 7-zip probably just ignored some errors in TAR archive.
You can upload some small "bad" tar archive for me and I'll check it.
Strangely, basic-bsdtar (static linked against liblzma 4.999beta9??) works like a champ with both the previously mentioned jruby and scala gzipped tar files.
As much as I'm a fan of 7-zip I still think there's a bug lurking in 9.15's handling of tars.
https://sourceforge.net/projects/mingw/files/MinGW/Utilities/basic%20bsdtar/basic-bsdtar-2.8.3-1/
Using 7za.exe v4.65 I'm able to successfully extract things like the following. Using 7za.exe v9.15 gives me an
when attempting to extract from the tar
What was the decision on this one? Is it a bug? Should I file something in the tracker? Something else?
Jon
Probably you should report authors of these TARs, thjat these TARs are incorrect.
I'd like to be able to report these as bad TARs, but my testing shows only 7-Zip v9.15 has problems handling the example files.
7-Zip v4.65, basic-bsdtar (MinGW), and tar (MSYS) all seem to process these files fine.
Based on what I've found, I can't with a straight face report that the TARs are incorrect only because 7-Zip v9.15 doesn't seem to be able to process.
Thanks for checking into it and I'll just wait and look at how the next 9.xy beta version handles things.
Jon
"scala-2.8.0.final-devel-docs(2).tar":
junk after hex offset 7c22600
and, for example, two copies of scala-2.8.0.final-devel-docs/tools/scalap.html.
Second copy in junk block.
"jruby-bin-1.5.1(2).tar" same problem:
junk after hex offset 2771200
So just ask authors of these files why they use incorrect TAR software.
I'll pass the info along to both groups and refer them back to this discussion.
Odd that v4.65, basic-bsdtar, and gnu tar don't all choke on the junk blocks similar to v9.15.
Thanks for the details.
So 7-zip 9.15 is better:
1) It extracts good TAR archives.
2) It shows that some TAR archives are "bad". So users can ask developers of "bad" software to fix bugs.
Hello !
I have exactly the same problem with 7zip 9.15 and 9.16 on other tar files ; for instance, those coming from SF project "Java Service Wrapper".
I went back to 7zip 4.65 because of this…
I think it will be a problem to ask all developers over the world to fix their tar archives ;-)
Best regards
We must ask developers about version of TAR software that was used to create these "bad" archives.
And then we can ask these TAR software developers to fix bugs.
ipavlov
Can I ask where are you getting your tar file format definition from? Can you post a link to it here please.
Every other tar program that I've used will open my tar files perfectly fine except for 7-zip 9.15 and later.
Are saying that it's the fault of every other tar file manufacturer except yourself? If so please show us the proof.
7-zip is a great application, and we all appreciate the hard work and effort that you've put in over the years, but this broken tar file support is getting beyond a joke.
Please please please either fix it, or give us the option to support so called "broken" tar files.