Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 23461 invoked from network); 7 Aug 2006 14:03:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Aug 2006 14:03:35 -0000 Received: (qmail 2013 invoked by uid 500); 7 Aug 2006 14:03:34 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 1968 invoked by uid 500); 7 Aug 2006 14:03:34 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 1957 invoked by uid 99); 7 Aug 2006 14:03:33 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Aug 2006 07:03:33 -0700 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Aug 2006 07:03:33 -0700 Received: by brutus.apache.org (Postfix, from userid 33) id 8345B7142CC; Mon, 7 Aug 2006 14:00:52 +0000 (GMT) From: bugzilla@apache.org To: dev@ant.apache.org Subject: DO NOT REPLY [Bug 40195] - Tar task leaves garbage at end of archive In-Reply-To: X-Bugzilla-Reason: AssignedTo Message-Id: <20060807140052.8345B7142CC@brutus.apache.org> Date: Mon, 7 Aug 2006 14:00:52 +0000 (GMT) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=40195 ------- Additional Comments From gudnabrsam@yahoo.com 2006-08-07 14:00 ------- You should probably add more information until we have enough to be able to reproduce the problem. Such as: a sample buildfile that creates a tar with the named problem (even if that is _any_ Ant-generated tar every bit you can do is helpful). Information as to _which_ 'buggy tar implementations' 'complain or do unexpected things', as well as _what_ complaints they issue/unexpected things they do, is also necessary. Finally, if you feel these events take place with "buggy tar implementations," what would you expect Ant to do about _them_? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org