git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Systems with non-posix TAR implementations: How to handle

From
TATor Arntsen <tor@spacetec.no>
Date
Apr 26, 2010, 15:55 UTC
Message-ID
<s2sd2d39d861004260855l2ca5799fj7dfa70799ff1f307@mail.gmail.com>

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: René Scharfe
Message 1 of 3 in “Systems with non-posix TAR implementations: How to handle”
  1. Tor ArntsenApr 26, 2010
  2. René ScharfeApr 26, 2010
  3. Tor ArntsenApr 27, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.