Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Yes, but you are probably not aware that RAR can open tar.gz files without a problem, only in this case it indicates corruption. How would you that under Linux?
If you type "tar -tzf somefile.tar.gz" under Linux, you'll get a listing of the contents of the archive.
If you downloaded the tarball under Windows IE, be aware that IE may have extracted the GZIP compression and what you have may be an uncompressed tar file instead of a compressed one -- but the contents would still be okay. I don't know why IE does this "favor" for you, because the target file takes up a *lot* more space on disk, but....that's Micro$oft.
In any case, if "tar -tzf somefile.tar.gz" fails, try "tar -tf somefile.tar.gz". If this second command works, then rename the file to "somefile.tar" and you're good to go.
I'm almost 100% certain the problem is with your download or local extraction process, because the Drupal web site creates these tarballs automatically every night. The odds of one tarball being defective with a process that works successfully tens of thousands of times in a row are extremely small. (The programmers don't upload the tarballs -- we just commit source to CVS, and drupal.org has a batch job that automatically makes tarballs.)
By the way, the tarball is now known to be okay on the server. I have a test report from another user who successfully downloaded and installed this version.
Comments
Comment #1
syscrusher commentedIt's a TAR file, compressed with GZIP, not a RAR file.
Scott
Comment #2
ñull commentedYes, but you are probably not aware that RAR can open tar.gz files without a problem, only in this case it indicates corruption. How would you that under Linux?
Comment #3
ñull commentedI meant: How would you test for corruption under Linux?
Comment #4
syscrusher commentedIf you type "tar -tzf somefile.tar.gz" under Linux, you'll get a listing of the contents of the archive.
If you downloaded the tarball under Windows IE, be aware that IE may have extracted the GZIP compression and what you have may be an uncompressed tar file instead of a compressed one -- but the contents would still be okay. I don't know why IE does this "favor" for you, because the target file takes up a *lot* more space on disk, but....that's Micro$oft.
In any case, if "tar -tzf somefile.tar.gz" fails, try "tar -tf somefile.tar.gz". If this second command works, then rename the file to "somefile.tar" and you're good to go.
I'm almost 100% certain the problem is with your download or local extraction process, because the Drupal web site creates these tarballs automatically every night. The odds of one tarball being defective with a process that works successfully tens of thousands of times in a row are extremely small. (The programmers don't upload the tarballs -- we just commit source to CVS, and drupal.org has a batch job that automatically makes tarballs.)
Scott
Comment #5
syscrusher commentedBy the way, the tarball is now known to be okay on the server. I have a test report from another user who successfully downloaded and installed this version.
Comment #6
ñull commentedMust have been a glitch. I downloaded anew and now RAR tests it without errors.
Comment #7
syscrusher commentedTerrific! Thanks for the un-error report. I'll close this issue.