Your message dated Tue, 14 Jun 2005 23:39:02 -0600 (MDT)
with message-id <[EMAIL PROTECTED]>
and subject line fixed in 1.15.1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 3 Apr 2005 15:09:13 +0000
>From [EMAIL PROTECTED] Sun Apr 03 08:09:13 2005
Return-path: <[EMAIL PROTECTED]>
Received: from bender.bawue.de [193.7.176.20] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DI6iu-0005IB-00; Sun, 03 Apr 2005 08:09:12 -0700
Received: by bender.bawue.de (Postfix, from userid 10)
        id 1BC14444E8; Sun,  3 Apr 2005 17:09:11 +0200 (MEST)
Received: by mobile-mx.n-dimensional.de (Postfix, from userid 1001)
        id D90FA71775; Sun,  3 Apr 2005 17:05:08 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Hans Ulrich Niedermann <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: tar silently moves files with path > 99 chars
X-Mailer: reportbug 3.8
Date: Sun, 03 Apr 2005 17:05:08 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: tar
Version: 1.13.93-4
Severity: normal


Abstract:
=========

If the path to a file is longer than 99 characters, then

  * tar 1.13.93-4 (Sarge):
    a) silently cuts all the path components and adds the file to the
       top of the tarball
    b) prints *no* error message
    c) exits with error code 0, i.e. "successful"
  * tar 1.14-2 (Sid):
    a) creates the archive without the file
    b) prints an error message expressing the cause of the problem
    c) exits with error code != 0, i.e. "error"


Details:
========

I noticed this bug while creating a source tarball via "make dist" on an
automake-based package using stock automake1.9 and tar from Sarge.

The file in question should have been

    
libexif-testsuite-0.6.13/src/libgphoto2/libgphoto2_port/libgphoto2_port/gphoto2-port-portability-os2.h

in the tarball would always be packaged as

    gphoto2-port-portability-os2.h

Fortunately, I found the automake bug #302682 which talks about newer
tar supporting more tar formats:

   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302682

This prompted me to test the newer tar version 1.14-2 from Sid. The
results point to a definite problem in tar:

tardir=libexif-testsuite-0.6.13 && /bin/sh 
/home/uli/src/photo/libexif-testsuite/missing --run tar chof - "$tardir" | 
GZIP=--best gzip -c >libexif-testsuite-0.6.13.tar.gz
tar: 
libexif-testsuite-0.6.13/src/libgphoto2/libgphoto2_port/libgphoto2_port/gphoto2-port-portability-o2.h:
 file name is too long (max 99); not dumped
tar: Error exit delayed from previous errors
tardir=libexif-testsuite-0.6.13 && /bin/sh 
/home/uli/src/photo/libexif-testsuite/missing --run tar chof - "$tardir" | 
bzip2 -9 -c >libexif-testsuite-0.6.13.tar.bz2 tar: 
libexif-testsuite-0.6.13/src/libgphoto2/libgphoto2_port/libgphoto2_port/gphoto2-port-portability-o2.h:
 file name is too long (max 99); not dumped


Conclusion:
===========

I can understand if the file format only allows 99 characters for the
path. However, tar 1.13.93 handles that in a completely wrong way.

Even tar 1.13.93 should definitely fail with an error message instead
of just silently moving the offending file around and pretend nothing
bad ever happened.


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (100, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-rc2-vs1.9.4-rc3-ndim-1
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages tar depends on:
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries an

-- no debconf information

---------------------------------------
Received: (at 302883-done) by bugs.debian.org; 15 Jun 2005 05:38:54 +0000
>From [EMAIL PROTECTED] Tue Jun 14 22:38:53 2005
Return-path: <[EMAIL PROTECTED]>
Received: from winfree.gag.com [192.133.104.8] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DiQc1-0003dU-00; Tue, 14 Jun 2005 22:38:53 -0700
Received: from localhost (localhost [127.0.0.1])
        by winfree.gag.com (Postfix) with ESMTP id 76426C471;
        Tue, 14 Jun 2005 23:38:53 -0600 (MDT)
Received: from winfree.gag.com ([127.0.0.1])
        by localhost (winfree [127.0.0.1]) (amavisd-new, port 10024)
        with ESMTP id 24804-02; Tue, 14 Jun 2005 23:38:52 -0600 (MDT)
Received: from rover.gag.com (localhost [127.0.0.1])
        by winfree.gag.com (Postfix) with ESMTP id 018F0C3AE;
        Tue, 14 Jun 2005 23:38:52 -0600 (MDT)
Received: by rover.gag.com (Postfix, from userid 1000)
        id 4D37FE6D09; Tue, 14 Jun 2005 23:39:02 -0600 (MDT)
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: fixed in 1.15.1
Message-Id: <[EMAIL PROTECTED]>
Date: Tue, 14 Jun 2005 23:39:02 -0600 (MDT)
From: [EMAIL PROTECTED] (Bdale Garbee)
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at gag.com
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-2.0 required=4.0 tests=BAYES_01 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 4

Testing with 1.15.1 confirms that these problems no longer exist.

Bdale


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to