{"thread":{"id":"23607","subject":"Systems with non-posix TAR implementations: How to handle","startedAt":"2010-04-26T15:55:44Z","lastAt":"2010-04-27T16:18:59Z","messageCount":3,"participants":["Tor Arntsen","René Scharfe"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"140421","messageId":"s2sd2d39d861004260855l2ca5799fj7dfa70799ff1f307@mail.gmail.com","threadId":"23607","inReplyTo":null,"subject":"Systems with non-posix TAR implementations: How to handle","fromName":"Tor Arntsen","fromEmail":"tor@spacetec.no","sentAt":"2010-04-26T15:55:44Z","receivedAt":"2010-04-26T15:55:44Z","isPatch":false,"sender":{"key":"tor@spacetec.no","avatar":null},"body":"Ref. the testlog that I posted in the thread \"[PATCH] Add Tru64/OSF1\nsupport in Makefile\"\n\n*** t0024-crlf-archive.sh ***\n*   ok 1: setup\n* FAIL 2: tar archive\n\n\n               git archive --format=tar HEAD |\n               ( mkdir untarred && cd untarred && \"$TAR\" -xf - )\n\n               test_cmp sample untarred/sample\n\n\n *   ok 3: zip archive.\n\nThe problem with that test is that the Tru64 V5.1 'tar' says 'This\ndoesn't look like a tar archive' on the generated file. However, it\nturns out that the tar file generated by 'git archive --format=tar' is\nfine, it's just that it's a POSIX tar archive and the Tru64 'tar'\nprogram isn't POSIX tar format compatible.\nHow should we handle this? Just ignore errors in this test on Tru64,\nor is there some other way that I missed?\n\n-Tor\n"},{"id":"140429","messageId":"4BD5D25F.904@lsrfire.ath.cx","threadId":"23607","inReplyTo":"s2sd2d39d861004260855l2ca5799fj7dfa70799ff1f307@mail.gmail.com","subject":"Re: Systems with non-posix TAR implementations: How to handle","fromName":"René Scharfe","fromEmail":"rene.scharfe@lsrfire.ath.cx","sentAt":"2010-04-26T17:50:23Z","receivedAt":"2010-04-26T17:50:23Z","isPatch":false,"sender":{"key":"l.s.r@web.de","avatar":"https://avatars.githubusercontent.com/u/26122331?v=4"},"body":"Am 26.04.2010 17:55, schrieb Tor Arntsen:\n> Ref. the testlog that I posted in the thread \"[PATCH] Add Tru64/OSF1\n> support in Makefile\"\n> \n> *** t0024-crlf-archive.sh ***\n> *   ok 1: setup\n> * FAIL 2: tar archive\n> \n> \n>                git archive --format=tar HEAD |\n>                ( mkdir untarred && cd untarred && \"$TAR\" -xf - )\n> \n>                test_cmp sample untarred/sample\n> \n> \n>  *   ok 3: zip archive.\n> \n> The problem with that test is that the Tru64 V5.1 'tar' says 'This\n> doesn't look like a tar archive' on the generated file. However, it\n> turns out that the tar file generated by 'git archive --format=tar' is\n> fine, it's just that it's a POSIX tar archive and the Tru64 'tar'\n> program isn't POSIX tar format compatible.\n> How should we handle this? Just ignore errors in this test on Tru64,\n> or is there some other way that I missed?\n\nThat depends: if you just want to make sure that the test works fine,\nyou could install GNU tar, perhaps as gtar, and let TAR in Makefile (or\nconfig.mak) point to it.  If the test fails with a tar that understands\nthe format then you've found a bug.\n\nIt could get a bit more complicated if you want to use git archive to\ncreate tar files that the native tar can understand.  For most repos it\nshould be sufficient to specify a tree instead of a commit, e.g. with an\nadded colon:\n\n\tgit archive -o archive-without-comment.tar HEAD:\n\nThis makes git archive leave out the comment entry, which might upset\nsome tar implementations.  I don't know if that's sufficient to make\nTru64 tar happy, though.\n\nRené\n"},{"id":"140525","messageId":"t2md2d39d861004270918o27ffc34ci282df4714edd0097@mail.gmail.com","threadId":"23607","inReplyTo":"4BD5D25F.904@lsrfire.ath.cx","subject":"Re: Systems with non-posix TAR implementations: How to handle","fromName":"Tor Arntsen","fromEmail":"tor@spacetec.no","sentAt":"2010-04-27T16:18:59Z","receivedAt":"2010-04-27T16:18:59Z","isPatch":false,"sender":{"key":"tor@spacetec.no","avatar":null},"body":"On Mon, Apr 26, 2010 at 19:50, René Scharfe <rene.scharfe@lsrfire.ath.cx> wrote:\n> Am 26.04.2010 17:55, schrieb Tor Arntsen:\n[..]\n>> *** t0024-crlf-archive.sh ***\n>> *   ok 1: setup\n>> * FAIL 2: tar archive\n[..]\n>> The problem with that test is that the Tru64 V5.1 'tar' says 'This\n>> doesn't look like a tar archive' on the generated file. However, it\n>> turns out that the tar file generated by 'git archive --format=tar' is\n>> fine, it's just that it's a POSIX tar archive and the Tru64 'tar'\n>> program isn't POSIX tar format compatible.\n>> How should we handle this? Just ignore errors in this test on Tru64,\n>> or is there some other way that I missed?\n>\n> That depends: if you just want to make sure that the test works fine,\n> you could install GNU tar, perhaps as gtar, and let TAR in Makefile (or\n> config.mak) point to it.  If the test fails with a tar that understands\n> the format then you've found a bug.\n\nDone. Everything's fine with gtar. As far as the OSF1 'make test' is\nconcerned I've re-run it with gtar, native compiler and\nSHELL_PATH=<self-compiled-bash>, and everything looks fine except some\nUTF8 conversion tests which may be caused by some iconv lib issues on\nthis platform.\n\n> It could get a bit more complicated if you want to use git archive to\n> create tar files that the native tar can understand.  For most repos it\n> should be sufficient to specify a tree instead of a commit, e.g. with an\n> added colon:\n>\n>        git archive -o archive-without-comment.tar HEAD:\n>\n> This makes git archive leave out the comment entry, which might upset\n> some tar implementations.  I don't know if that's sufficient to make\n> Tru64 tar happy, though.\n\nIt indeed is happy with that, this will be very useful to know when\nworking on OSF1 and only having the native tar application.\n\nThanks,\n-Tor\n"}]}