From: Tor Arntsen <tor@spacetec.no>
To: git@vger.kernel.org
Subject: Systems with non-posix TAR implementations: How to handle
Date: Mon, 26 Apr 2010 17:55:44 +0200 [thread overview]
Message-ID: <s2sd2d39d861004260855l2ca5799fj7dfa70799ff1f307@mail.gmail.com> (raw)
Ref. the testlog that I posted in the thread "[PATCH] Add Tru64/OSF1
support in Makefile"
*** t0024-crlf-archive.sh ***
* ok 1: setup
* FAIL 2: tar archive
git archive --format=tar HEAD |
( mkdir untarred && cd untarred && "$TAR" -xf - )
test_cmp sample untarred/sample
* ok 3: zip 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=tar' 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?
-Tor
next reply other threads:[~2010-04-26 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 15:55 Tor Arntsen [this message]
2010-04-26 17:50 ` Systems with non-posix TAR implementations: How to handle René Scharfe
2010-04-27 16:18 ` Tor Arntsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s2sd2d39d861004260855l2ca5799fj7dfa70799ff1f307@mail.gmail.com \
--to=tor@spacetec.no \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).