From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#258: [22.2]: visiting boost_1_35_0.tar.bz2 causes an error Date: Sat, 24 May 2008 13:34:47 +0300 Message-ID: References: <6EE216E1AA959543A555C60FF34FB767042FB5EC@maileube01.misys.global.ad> Reply-To: Eli Zaretskii , 258@emacsbugs.donarmstrong.com NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1211626326 2755 80.91.229.12 (24 May 2008 10:52:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 24 May 2008 10:52:06 +0000 (UTC) Cc: 258@emacsbugs.donarmstrong.com, Simon.Marshall@misys.com, bug-submit-list@donarmstrong.com, bug-gnu-emacs@gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat May 24 12:52:46 2008 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JzrMf-0002Zh-VW for geb-bug-gnu-emacs@m.gmane.org; Sat, 24 May 2008 12:52:42 +0200 Original-Received: from localhost ([127.0.0.1]:58267 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JzrLv-0002v8-6c for geb-bug-gnu-emacs@m.gmane.org; Sat, 24 May 2008 06:51:55 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JzrLq-0002uM-73 for bug-gnu-emacs@gnu.org; Sat, 24 May 2008 06:51:50 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JzrLn-0002rg-C5 for bug-gnu-emacs@gnu.org; Sat, 24 May 2008 06:51:49 -0400 Original-Received: from [199.232.76.173] (port=33016 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JzrLm-0002rU-Sv for bug-gnu-emacs@gnu.org; Sat, 24 May 2008 06:51:46 -0400 Original-Received: from rzlab.ucr.edu ([138.23.92.77]:58065) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JzrLl-0002L6-To for bug-gnu-emacs@gnu.org; Sat, 24 May 2008 06:51:46 -0400 Original-Received: from rzlab.ucr.edu (rzlab.ucr.edu [127.0.0.1]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id m4OApgT5004496; Sat, 24 May 2008 03:51:43 -0700 Original-Received: (from debbugs@localhost) by rzlab.ucr.edu (8.13.8/8.13.8/Submit) id m4OAj5K3002297; Sat, 24 May 2008 03:45:05 -0700 X-Loop: don@donarmstrong.com Resent-From: Eli Zaretskii Resent-To: bug-submit-list@donarmstrong.com Resent-CC: Emacs Bugs Resent-Date: Sat, 24 May 2008 10:45:05 +0000 Resent-Message-ID: Resent-Sender: don@donarmstrong.com X-Emacs-PR-Message: report 258 X-Emacs-PR-Package: emacs X-Emacs-PR-Keywords: moreinfo Original-Received: via spool by 258-submit@emacsbugs.donarmstrong.com id=B258.1211625357949 (code B ref 258); Sat, 24 May 2008 10:45:05 +0000 Original-Received: (at 258) by emacsbugs.donarmstrong.com; 24 May 2008 10:35:57 +0000 Original-Received: from mtaout6.012.net.il (mtaout6.012.net.il [84.95.2.16]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id m4OAZqTo000940 for <258@emacsbugs.donarmstrong.com>; Sat, 24 May 2008 03:35:53 -0700 Original-Received: from HOME-C4E4A596F7 ([80.230.149.132]) by i-mtaout6.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0K1D0016ZCQEZW70@i-mtaout6.012.net.il> for 258@emacsbugs.donarmstrong.com; Sat, 24 May 2008 13:49:27 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) Resent-Date: Sat, 24 May 2008 06:51:49 -0400 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:18129 Archived-At: > From: Stefan Monnier > Cc: 258@emacsbugs.donarmstrong.com, Simon.Marshall@misys.com, > bug-submit-list@donarmstrong.com, bug-gnu-emacs@gnu.org > Date: Wed, 21 May 2008 11:40:41 -0400 > > >> > It's the ustar format used by pax. We've bumped into this before, I > >> > think; search the archives. (It's strange, though: I'm quite sure I > >> > installed a stopgap fix in the last minute before v22.1 hit the FTP > >> > sites, so maybe I'm confused and this is another problem?) > >> > >> It doesn't look like the wiki's description of ustar. Do you know where > >> I could find a description of the format in that tarball? > > > Not at the moment, no. I will look. > > Please do, thank you. Sorry for a long delay. Here's what I found: . `file' says that this is a POSIX Tar file. . Looking at the description of Tar formats in Wikipedia (http://en.wikipedia.org/wiki/Tar_(file_format)), this appears to be the POSIX Tar format created by GNU Tar: the "ustar" signature that is not null-terminated is followed by 0x2020 as the "version". . Looking at the offending tarball with Hexl, I see the telltale "ustar " signature of the GNU Tar format, and all the other fields of the file headers look okay, just like described in the Wikipedia and in the other docs I could find on the net. So I don't understand why you said above that this tarball doesn't look like wiki's description of ustar. . The differences between POSIX and GNU Tar formats are minor, apart of the way the "ustar" signature is written, as long as sparse files or incremental archives are not used, and tar-mode.el already seems to support them both, at least in the current CVS. . The error message I get, both with today's CVS and with Emacs 22.1, is not the one cited at the beginning of this thread ("Debugger entered--Lisp error: (args-out-of-range -256589311 -256588799)"), but this one: Warning: premature EOF parsing tar file This warning is generated because this archive includes long names, signaled by the special pseudo-file name "././@LongLink", which is where the archive listing displayed by tar-mode for this tarball stops. So my conclusion is that we need to add support for "././@LongLink" magic file names, in order to fix this problem. (Btw, it looks like the archive which started this thread was created on MS-Windows, since the Owner/Group are Administrator/None, and the sizes of directories are zero.) > > In case you are right, and this _is_ GNU tar format, > > I don't know that it is but wikipedia seems to think that the "ustar " > indicates it's GNU Tar format. > > > it should be described in the GNU Tar docs, and maybe you will find > > more in the GNU Tar sources. > > I couldn't find it in GNU Tar's Texinfo doc (it does have some > description of tar-format, as well as discussions about various formats > w.r.t how well each one is supported and how to choose among them). > > Hopefully the source code has further info (well it surely does have, > in the form of actual code ;-), The place to look is in src/tar.h in the GNU Tar sources, in case someone is interested. As an aside, the way tar-mode formats the archive listing seems to assume a user name is no longer than 7 characters, because for longer names (and "Administrator" is longer), it doesn't leave any whitespace between the file mode bits and the owner name, like so: drwxrwxrwxAdministrator/None 0 boost_1_35_0/ drwxrwxrwxAdministrator/None 0 boost_1_35_0/boost/ drwxrwxrwxAdministrator/None 0 boost_1_35_0/boost/algorithm/ -rw-rw-rw-Administrator/None 1253 boost_1_35_0/boost/algorithm/minmax.hp\ p -rw-rw-rw-Administrator/None 17435 boost_1_35_0/boost/algorithm/minmax_el\ ement.hpp drwxrwxrwxAdministrator/None 0 boost_1_35_0/boost/algorithm/string/ I suggest to fix this.