From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tor Arntsen Subject: Re: Systems with non-posix TAR implementations: How to handle Date: Tue, 27 Apr 2010 18:18:59 +0200 Message-ID: References: <4BD5D25F.904@lsrfire.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: git@vger.kernel.org To: =?ISO-8859-1?Q?Ren=E9_Scharfe?= X-From: git-owner@vger.kernel.org Tue Apr 27 18:19:14 2010 connect(): No such file or directory Return-path: Envelope-to: gcvg-git-2@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1O6nVC-00030Q-7U for gcvg-git-2@lo.gmane.org; Tue, 27 Apr 2010 18:19:14 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756235Ab0D0QTG convert rfc822-to-quoted-printable (ORCPT ); Tue, 27 Apr 2010 12:19:06 -0400 Received: from mail-ew0-f220.google.com ([209.85.219.220]:43202 "EHLO mail-ew0-f220.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756144Ab0D0QTD convert rfc822-to-8bit (ORCPT ); Tue, 27 Apr 2010 12:19:03 -0400 Received: by ewy20 with SMTP id 20so4390290ewy.1 for ; Tue, 27 Apr 2010 09:19:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=7IXb5Cmuos2SanKZ+HCXfnvxamM2JKBeOkPuzEGOPQA=; b=e3gg8UYscOWfOuhQRoGJ/gBmwWPsttTojFN7Wy8rKM7q2KmZ0oEmxDz6tsd9EmuI57 GSd3vWa5Bx9DJMR2YOh9nTSpUhBFrImrnKYh8AbmhlLXbEv7X+W7FAz0gzJqGztcmflH Yt9oAxDCCDahyTLXhjgWhSxha8HP32G1ZL6cU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=NNRKfeBp/qzfGkfnaI5/l3LFmZ6niN5sqa45N4cKj36VhvesbK96ZtLmerCUtDhlPz iyG7X+PCL+uHvLSpi2j4DZAB9EbnsWnBQWsYU3zn63ZV00/P/qCFzltbnvZx7TaC9RU5 5xrCyHz/Zu1Nc5ElW71um04UNZsRDd8Cfoui0= Received: by 10.239.137.14 with SMTP id j14mr530527hbj.198.1272385139401; Tue, 27 Apr 2010 09:18:59 -0700 (PDT) Received: by 10.239.179.197 with HTTP; Tue, 27 Apr 2010 09:18:59 -0700 (PDT) In-Reply-To: <4BD5D25F.904@lsrfire.ath.cx> X-Google-Sender-Auth: 1da4c8bff0f80332 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Mon, Apr 26, 2010 at 19:50, Ren=E9 Scharfe wrote: > Am 26.04.2010 17:55, schrieb Tor Arntsen: [..] >> *** t0024-crlf-archive.sh *** >> * =A0 ok 1: setup >> * FAIL 2: tar archive [..] >> The problem with that test is that the Tru64 V5.1 'tar' says 'This >> doesn't look like a tar archive' on the generated file. However, it >> turns out that the tar file generated by 'git archive --format=3Dtar= ' is >> fine, it's just that it's a POSIX tar archive and the Tru64 'tar' >> program isn't POSIX tar format compatible. >> How should we handle this? Just ignore errors in this test on Tru64, >> or is there some other way that I missed? > > That depends: if you just want to make sure that the test works fine, > you could install GNU tar, perhaps as gtar, and let TAR in Makefile (= or > config.mak) point to it. =A0If the test fails with a tar that underst= ands > the format then you've found a bug. Done. Everything's fine with gtar. As far as the OSF1 'make test' is concerned I've re-run it with gtar, native compiler and SHELL_PATH=3D, and everything looks fine except som= e UTF8 conversion tests which may be caused by some iconv lib issues on this platform. > It could get a bit more complicated if you want to use git archive to > create tar files that the native tar can understand. =A0For most repo= s it > should be sufficient to specify a tree instead of a commit, e.g. with= an > added colon: > > =A0 =A0 =A0 =A0git archive -o archive-without-comment.tar HEAD: > > This makes git archive leave out the comment entry, which might upset > some tar implementations. =A0I don't know if that's sufficient to mak= e > Tru64 tar happy, though. It indeed is happy with that, this will be very useful to know when working on OSF1 and only having the native tar application. Thanks, -Tor