{"thread":{"id":"53386","subject":"Git 2.26.2 and failed self tests on OS X","startedAt":"2020-05-04T07:03:30Z","lastAt":"2020-05-07T04:12:20Z","messageCount":15,"participants":["Jeffrey Walton","Eric Sunshine","Carlo Marcelo Arenas Belón","Torsten Bögershausen","Philippe Blain"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"396888","messageId":"CAH8yC8myTMOetxgaj1wt0MbvSQ0LSRV0FHz4ywsBM1zzhUQG=w@mail.gmail.com","threadId":"53386","inReplyTo":null,"subject":"Git 2.26.2 and failed self tests on OS X","fromName":"Jeffrey Walton","fromEmail":"noloader@gmail.com","sentAt":"2020-05-04T07:03:01Z","receivedAt":"2020-05-04T07:03:30Z","isPatch":false,"sender":{"key":"noloader@gmail.com","avatar":null},"body":"Hi Everyone,\n\nI'm building Git 2.26.2 from sources on a Mac-mini with OS X 10.12.6\nand a PowerMac with OS X 10.5. Some of the t3902-quoted.sh tests are\nfailing.\n\nThe Mac-Mini uses Bash 3.2.57(1)-release. The PowerMac uses 3.2.17(1)-release.\n\nJeff\n\n*** t3902-quoted.sh ***\nnot ok 1 - setup\n#\n#\n#               mkdir \"$FN\" &&\n#               for_each_name \"echo initial >\\\"\\$name\\\"\" &&\n#               git add . &&\n#               git commit -q -m Initial &&\n#\n#               for_each_name \"echo second >\\\"\\$name\\\"\" &&\n#               git commit -a -m Second &&\n#\n#               for_each_name \"echo modified >\\\"\\$name\\\"\"\n#\n#\nok 2 - setup expected files\nnot ok 3 - check fully quoted output from ls-files\n#\n#\n#               git ls-files >current && test_cmp expect.quoted current\n#\n#\nnot ok 4 - check fully quoted output from diff-files\n#\n#\n#               git diff --name-only >current &&\n#               test_cmp expect.quoted current\n#\n#\nnot ok 5 - check fully quoted output from diff-index\n#\n#\n#               git diff --name-only HEAD >current &&\n#               test_cmp expect.quoted current\n#\n#\nnot ok 6 - check fully quoted output from diff-tree\n#\n#\n#               git diff --name-only HEAD^ HEAD >current &&\n#               test_cmp expect.quoted current\n#\n#\nnot ok 7 - check fully quoted output from ls-tree\n#\n#\n#               git ls-tree --name-only -r HEAD >current &&\n#               test_cmp expect.quoted current\n#\n#\nok 8 - setting core.quotepath\nnot ok 9 - check fully quoted output from ls-files\n#\n#\n#               git ls-files >current && test_cmp expect.raw current\n#\n#\nnot ok 10 - check fully quoted output from diff-files\n#\n#\n#               git diff --name-only >current &&\n#               test_cmp expect.raw current\n#\n#\nnot ok 11 - check fully quoted output from diff-index\n#\n#\n#               git diff --name-only HEAD >current &&\n#               test_cmp expect.raw current\n#\n#\nnot ok 12 - check fully quoted output from diff-tree\n#\n#\n#               git diff --name-only HEAD^ HEAD >current &&\n#               test_cmp expect.raw current\n#\n#\nnot ok 13 - check fully quoted output from ls-tree\n#\n#\n#               git ls-tree --name-only -r HEAD >current &&\n#               test_cmp expect.raw current\n#\n#\n# failed 11 among 13 test(s)\n1..13\nmake[2]: *** [t3902-quoted.sh] Error 1\nmake[1]: *** [test] Error 2\nmake: *** [test] Error 2\n"},{"id":"396909","messageId":"CAPig+cReUs5Ka-gw_hXJ0XZLBmPVjV_tzJkd+TWvdTX+N-inxg@mail.gmail.com","threadId":"53386","inReplyTo":"CAH8yC8myTMOetxgaj1wt0MbvSQ0LSRV0FHz4ywsBM1zzhUQG=w@mail.gmail.com","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2020-05-04T15:39:14Z","receivedAt":"2020-05-04T15:39:30Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"> I'm building Git 2.26.2 from sources on a Mac-mini with OS X 10.12.6\n> and a PowerMac with OS X 10.5. Some of the t3902-quoted.sh tests are\n> failing.\n>\n> *** t3902-quoted.sh ***\n> not ok 1 - setup\n> not ok 3 - check fully quoted output from ls-files\n> not ok 4 - check fully quoted output from diff-files\n> not ok 5 - check fully quoted output from diff-index\n> not ok 6 - check fully quoted output from diff-tree\n> not ok 7 - check fully quoted output from ls-tree\n> not ok 9 - check fully quoted output from ls-files\n> not ok 10 - check fully quoted output from diff-files\n> not ok 11 - check fully quoted output from diff-index\n> not ok 12 - check fully quoted output from diff-tree\n> not ok 13 - check fully quoted output from ls-tree\n\nI am unable to reproduce these failures on OS X 10.13.6.\n"},{"id":"396931","messageId":"20200504165214.GF86805@Carlos-MBP","threadId":"53386","inReplyTo":"CAH8yC8myTMOetxgaj1wt0MbvSQ0LSRV0FHz4ywsBM1zzhUQG=w@mail.gmail.com","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Carlo Marcelo Arenas Belón","fromEmail":"carenas@gmail.com","sentAt":"2020-05-04T16:52:14Z","receivedAt":"2020-05-04T16:52:20Z","isPatch":false,"sender":{"key":"carenas@gmail.com","avatar":"https://avatars.githubusercontent.com/u/76036?v=4"},"body":"On Mon, May 04, 2020 at 03:03:01AM -0400, Jeffrey Walton wrote:\n> \n> I'm building Git 2.26.2 from sources on a Mac-mini with OS X 10.12.6\n> and a PowerMac with OS X 10.5. Some of the t3902-quoted.sh tests are\n> failing.\n> \n> The Mac-Mini uses Bash 3.2.57(1)-release. The PowerMac uses 3.2.17(1)-release.\n\nif the problem is the bash version but you can build/install a newer one that\ndoesn't have this problem then you can get the test to use it by pointing to\nit with TEST_SHELL_PATH as in :\n\n  $ make TEST_SHELL_PATH=/usr/local/bin/bash test\n\nCarlo\n"},{"id":"396937","messageId":"CAPig+cSPXqvFg3-25aDzptuVOHmqOcnmsCKHgjMB9poPyJR2gw@mail.gmail.com","threadId":"53386","inReplyTo":"20200504165214.GF86805@Carlos-MBP","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2020-05-04T17:18:06Z","receivedAt":"2020-05-04T17:18:21Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Mon, May 4, 2020 at 12:52 PM Carlo Marcelo Arenas Belón\n<carenas@gmail.com> wrote:\n> On Mon, May 04, 2020 at 03:03:01AM -0400, Jeffrey Walton wrote:\n> > I'm building Git 2.26.2 from sources on a Mac-mini with OS X 10.12.6\n> > and a PowerMac with OS X 10.5. Some of the t3902-quoted.sh tests are\n> > failing.\n> >\n> > The Mac-Mini uses Bash 3.2.57(1)-release. The PowerMac uses 3.2.17(1)-release.\n>\n> if the problem is the bash version but you can build/install a newer one that\n> doesn't have this problem [...]\n\nMy OS X 10.13.6 has Bash 3.2.57, as well, and I'm unable to reproduce\nthese failures, so it seems fairly unlikely that the problem Jeffrey\nis seeing isn't tied to Bash.\n"},{"id":"396968","messageId":"20200504190830.g2tlrognjw6ddipo@tb-raspi4","threadId":"53386","inReplyTo":"CAPig+cSPXqvFg3-25aDzptuVOHmqOcnmsCKHgjMB9poPyJR2gw@mail.gmail.com","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2020-05-04T19:08:30Z","receivedAt":"2020-05-04T19:08:35Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On Mon, May 04, 2020 at 01:18:06PM -0400, Eric Sunshine wrote:\n> On Mon, May 4, 2020 at 12:52 PM Carlo Marcelo Arenas Belón\n> <carenas@gmail.com> wrote:\n> > On Mon, May 04, 2020 at 03:03:01AM -0400, Jeffrey Walton wrote:\n> > > I'm building Git 2.26.2 from sources on a Mac-mini with OS X 10.12.6\n> > > and a PowerMac with OS X 10.5. Some of the t3902-quoted.sh tests are\n> > > failing.\n> > >\n> > > The Mac-Mini uses Bash 3.2.57(1)-release. The PowerMac uses 3.2.17(1)-release.\n> >\n> > if the problem is the bash version but you can build/install a newer one that\n> > doesn't have this problem [...]\n>\n> My OS X 10.13.6 has Bash 3.2.57, as well, and I'm unable to reproduce\n> these failures, so it seems fairly unlikely that the problem Jeffrey\n> is seeing isn't tied to Bash.\n\nShould I read this as\n\".. seems fairly likely that the problem Jeffrey is seeing is tied to bash\" ?\n\nI can't reproduce it either, so my reasoning would rather be\n\"The problem is probably not caused by the shipped bash version\"\n\nIt could be something in the environemt, that confuses our tests here.\n\nDoes\n./t3902-quoted.sh   -v -d\ngive anything useful ?\n"},{"id":"396972","messageId":"CAPig+cS-zZGGwaX3wKyagnr+9=SSAcECi6GaO2+5T4OVR3vohA@mail.gmail.com","threadId":"53386","inReplyTo":"20200504190830.g2tlrognjw6ddipo@tb-raspi4","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2020-05-04T19:19:36Z","receivedAt":"2020-05-04T19:19:50Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Mon, May 4, 2020 at 3:08 PM Torsten Bögershausen <tboegi@web.de> wrote:\n> On Mon, May 04, 2020 at 01:18:06PM -0400, Eric Sunshine wrote:\n> > My OS X 10.13.6 has Bash 3.2.57, as well, and I'm unable to reproduce\n> > these failures, so it seems fairly unlikely that the problem Jeffrey\n> > is seeing isn't tied to Bash.\n>\n> Should I read this as\n> \".. seems fairly likely that the problem Jeffrey is seeing is tied to bash\" ?\n\nYes, applying s/unlikely/likely/ to my statement is the correct\ninterpretation. (Last-second editing strikes again.)\n"},{"id":"396973","messageId":"CAH8yC8=zsbXDVV99tdBMHwEhr-=dO=wrwBYZi=0J8iFmUHkk=g@mail.gmail.com","threadId":"53386","inReplyTo":"20200504190830.g2tlrognjw6ddipo@tb-raspi4","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Jeffrey Walton","fromEmail":"noloader@gmail.com","sentAt":"2020-05-04T19:20:11Z","receivedAt":"2020-05-04T19:20:42Z","isPatch":false,"sender":{"key":"noloader@gmail.com","avatar":null},"body":"On Mon, May 4, 2020 at 3:08 PM Torsten Bögershausen <tboegi@web.de> wrote:\n>\n> On Mon, May 04, 2020 at 01:18:06PM -0400, Eric Sunshine wrote:\n> > On Mon, May 4, 2020 at 12:52 PM Carlo Marcelo Arenas Belón\n> > <carenas@gmail.com> wrote:\n> > > On Mon, May 04, 2020 at 03:03:01AM -0400, Jeffrey Walton wrote:\n> > > > I'm building Git 2.26.2 from sources on a Mac-mini with OS X 10.12.6\n> > > > and a PowerMac with OS X 10.5. Some of the t3902-quoted.sh tests are\n> > > > failing.\n> > > >\n> > > > The Mac-Mini uses Bash 3.2.57(1)-release. The PowerMac uses 3.2.17(1)-release.\n> > >\n> > > if the problem is the bash version but you can build/install a newer one that\n> > > doesn't have this problem [...]\n> >\n> > My OS X 10.13.6 has Bash 3.2.57, as well, and I'm unable to reproduce\n> > these failures, so it seems fairly unlikely that the problem Jeffrey\n> > is seeing isn't tied to Bash.\n>\n> Should I read this as\n> \".. seems fairly likely that the problem Jeffrey is seeing is tied to bash\" ?\n>\n> I can't reproduce it either, so my reasoning would rather be\n> \"The problem is probably not caused by the shipped bash version\"\n>\n> It could be something in the environemt, that confuses our tests here.\n>\n> Does\n> ./t3902-quoted.sh   -v -d\n> give anything useful ?\n\nYes, it looks like the command reveals a couple of problems.\n\nI'll have to look into my iconv recipe. It has not changed in a while,\nso something else may be responsible for the failure.\nhttps://github.com/noloader/Build-Scripts/blob/master/build-iconv.sh.\n\nI'm not sure what to do with the HEAD problems.\n\n$ ./t3902-quoted.sh   -v -d\nInitialized empty Git repository in\n/Users/jwalton/Build-Scripts/git-2.26.2/t/trash\ndirectory.t3902-quoted/.git/\nexpecting success of 3902.1 'setup':\n\n        mkdir \"$FN\" &&\n        for_each_name \"echo initial >\\\"\\$name\\\"\" &&\n        git add . &&\n        git commit -q -m Initial &&\n\n        for_each_name \"echo second >\\\"\\$name\\\"\" &&\n        git commit -a -m Second &&\n\n        for_each_name \"echo modified >\\\"\\$name\\\"\"\n\n\nfatal: iconv_open(UTF-8,UTF-8-MAC) failed, but needed:\n    precomposed unicode is not supported.\n    If you want to use decomposed unicode, run\n    \"git config core.precomposeunicode false\"\n\nnot ok 1 - setup\n#\n#\n#               mkdir \"$FN\" &&\n#               for_each_name \"echo initial >\\\"\\$name\\\"\" &&\n#               git add . &&\n#               git commit -q -m Initial &&\n#\n#               for_each_name \"echo second >\\\"\\$name\\\"\" &&\n#               git commit -a -m Second &&\n#\n#               for_each_name \"echo modified >\\\"\\$name\\\"\"\n#\n#\n\nexpecting success of 3902.2 'setup expected files':\ncat >expect.quoted <<\\EOF &&\nName\n\"Name and a\\nLF\"\n\"Name and an\\tHT\"\n\"Name\\\"\"\nWith SP in it\n\"\\346\\277\\261\\351\\207\\216\\t\\347\\264\\224\"\n\"\\346\\277\\261\\351\\207\\216\\n\\347\\264\\224\"\n\"\\346\\277\\261\\351\\207\\216 \\347\\264\\224\"\n\"\\346\\277\\261\\351\\207\\216\\\"\\347\\264\\224\"\n\"\\346\\277\\261\\351\\207\\216/file\"\n\"\\346\\277\\261\\351\\207\\216\\347\\264\\224\"\nEOF\n\ncat >expect.raw <<\\EOF\nName\n\"Name and a\\nLF\"\n\"Name and an\\tHT\"\n\"Name\\\"\"\nWith SP in it\n\"濱野\\t純\"\n\"濱野\\n純\"\n濱野 純\n\"濱野\\\"純\"\n濱野/file\n濱野純\nEOF\n\nok 2 - setup expected files\n\nexpecting success of 3902.3 'check fully quoted output from ls-files':\n\n        git ls-files >current && test_cmp expect.quoted current\n\n\n--- expect.quoted       2020-05-04 19:14:39.000000000 +0000\n+++ current     2020-05-04 19:14:39.000000000 +0000\n@@ -1,11 +0,0 @@\n-Name\n-\"Name and a\\nLF\"\n-\"Name and an\\tHT\"\n-\"Name\\\"\"\n-With SP in it\n-\"\\346\\277\\261\\351\\207\\216\\t\\347\\264\\224\"\n-\"\\346\\277\\261\\351\\207\\216\\n\\347\\264\\224\"\n-\"\\346\\277\\261\\351\\207\\216 \\347\\264\\224\"\n-\"\\346\\277\\261\\351\\207\\216\\\"\\347\\264\\224\"\n-\"\\346\\277\\261\\351\\207\\216/file\"\n-\"\\346\\277\\261\\351\\207\\216\\347\\264\\224\"\nnot ok 3 - check fully quoted output from ls-files\n#\n#\n#               git ls-files >current && test_cmp expect.quoted current\n#\n#\n\nexpecting success of 3902.4 'check fully quoted output from diff-files':\n\n        git diff --name-only >current &&\n        test_cmp expect.quoted current\n\n\n--- expect.quoted       2020-05-04 19:14:39.000000000 +0000\n+++ current     2020-05-04 19:14:39.000000000 +0000\n@@ -1,11 +0,0 @@\n-Name\n-\"Name and a\\nLF\"\n-\"Name and an\\tHT\"\n-\"Name\\\"\"\n-With SP in it\n-\"\\346\\277\\261\\351\\207\\216\\t\\347\\264\\224\"\n-\"\\346\\277\\261\\351\\207\\216\\n\\347\\264\\224\"\n-\"\\346\\277\\261\\351\\207\\216 \\347\\264\\224\"\n-\"\\346\\277\\261\\351\\207\\216\\\"\\347\\264\\224\"\n-\"\\346\\277\\261\\351\\207\\216/file\"\n-\"\\346\\277\\261\\351\\207\\216\\347\\264\\224\"\nnot ok 4 - check fully quoted output from diff-files\n#\n#\n#               git diff --name-only >current &&\n#               test_cmp expect.quoted current\n#\n#\n\nexpecting success of 3902.5 'check fully quoted output from diff-index':\n\n        git diff --name-only HEAD >current &&\n        test_cmp expect.quoted current\n\n\nfatal: ambiguous argument 'HEAD': unknown revision or path not in the\nworking tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]'\nnot ok 5 - check fully quoted output from diff-index\n#\n#\n#               git diff --name-only HEAD >current &&\n#               test_cmp expect.quoted current\n#\n#\n\nexpecting success of 3902.6 'check fully quoted output from diff-tree':\n\n        git diff --name-only HEAD^ HEAD >current &&\n        test_cmp expect.quoted current\n\n\nfatal: ambiguous argument 'HEAD^': unknown revision or path not in the\nworking tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]'\nnot ok 6 - check fully quoted output from diff-tree\n#\n#\n#               git diff --name-only HEAD^ HEAD >current &&\n#               test_cmp expect.quoted current\n#\n#\n\nexpecting success of 3902.7 'check fully quoted output from ls-tree':\n\n        git ls-tree --name-only -r HEAD >current &&\n        test_cmp expect.quoted current\n\n\nfatal: Not a valid object name HEAD\nnot ok 7 - check fully quoted output from ls-tree\n#\n#\n#               git ls-tree --name-only -r HEAD >current &&\n#               test_cmp expect.quoted current\n#\n#\n\nexpecting success of 3902.8 'setting core.quotepath':\n\n        git config --bool core.quotepath false\n\n\nok 8 - setting core.quotepath\n\nexpecting success of 3902.9 'check fully quoted output from ls-files':\n\n        git ls-files >current && test_cmp expect.raw current\n\n\n--- expect.raw  2020-05-04 19:14:39.000000000 +0000\n+++ current     2020-05-04 19:14:40.000000000 +0000\n@@ -1,11 +0,0 @@\n-Name\n-\"Name and a\\nLF\"\n-\"Name and an\\tHT\"\n-\"Name\\\"\"\n-With SP in it\n-\"濱野\\t純\"\n-\"濱野\\n純\"\n-濱野 純\n-\"濱野\\\"純\"\n-濱野/file\n-濱野純\nnot ok 9 - check fully quoted output from ls-files\n#\n#\n#               git ls-files >current && test_cmp expect.raw current\n#\n#\n\nexpecting success of 3902.10 'check fully quoted output from diff-files':\n\n        git diff --name-only >current &&\n        test_cmp expect.raw current\n\n\n--- expect.raw  2020-05-04 19:14:39.000000000 +0000\n+++ current     2020-05-04 19:14:40.000000000 +0000\n@@ -1,11 +0,0 @@\n-Name\n-\"Name and a\\nLF\"\n-\"Name and an\\tHT\"\n-\"Name\\\"\"\n-With SP in it\n-\"濱野\\t純\"\n-\"濱野\\n純\"\n-濱野 純\n-\"濱野\\\"純\"\n-濱野/file\n-濱野純\nnot ok 10 - check fully quoted output from diff-files\n#\n#\n#               git diff --name-only >current &&\n#               test_cmp expect.raw current\n#\n#\n\nexpecting success of 3902.11 'check fully quoted output from diff-index':\n\n        git diff --name-only HEAD >current &&\n        test_cmp expect.raw current\n\n\nfatal: ambiguous argument 'HEAD': unknown revision or path not in the\nworking tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]'\nnot ok 11 - check fully quoted output from diff-index\n#\n#\n#               git diff --name-only HEAD >current &&\n#               test_cmp expect.raw current\n#\n#\n\nexpecting success of 3902.12 'check fully quoted output from diff-tree':\n\n        git diff --name-only HEAD^ HEAD >current &&\n        test_cmp expect.raw current\n\n\nfatal: ambiguous argument 'HEAD^': unknown revision or path not in the\nworking tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]'\nnot ok 12 - check fully quoted output from diff-tree\n#\n#\n#               git diff --name-only HEAD^ HEAD >current &&\n#               test_cmp expect.raw current\n#\n#\n\nexpecting success of 3902.13 'check fully quoted output from ls-tree':\n\n        git ls-tree --name-only -r HEAD >current &&\n        test_cmp expect.raw current\n\n\nfatal: Not a valid object name HEAD\nnot ok 13 - check fully quoted output from ls-tree\n#\n#\n#               git ls-tree --name-only -r HEAD >current &&\n#               test_cmp expect.raw current\n#\n#\n\n# failed 11 among 13 test(s)\n1..13\n"},{"id":"396979","messageId":"20200504201944.gh3zykhil3txdwnk@tb-raspi4","threadId":"53386","inReplyTo":"CAH8yC8=zsbXDVV99tdBMHwEhr-=dO=wrwBYZi=0J8iFmUHkk=g@mail.gmail.com","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2020-05-04T20:19:44Z","receivedAt":"2020-05-04T20:19:50Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On Mon, May 04, 2020 at 03:20:11PM -0400, Jeffrey Walton wrote:\n> On Mon, May 4, 2020 at 3:08 PM Torsten Bögershausen <tboegi@web.de> wrote:\n> >\n> > On Mon, May 04, 2020 at 01:18:06PM -0400, Eric Sunshine wrote:\n> > > On Mon, May 4, 2020 at 12:52 PM Carlo Marcelo Arenas Belón\n> > > <carenas@gmail.com> wrote:\n> > > > On Mon, May 04, 2020 at 03:03:01AM -0400, Jeffrey Walton wrote:\n> > > > > I'm building Git 2.26.2 from sources on a Mac-mini with OS X 10.12.6\n> > > > > and a PowerMac with OS X 10.5. Some of the t3902-quoted.sh tests are\n> > > > > failing.\n> > > > >\n> > > > > The Mac-Mini uses Bash 3.2.57(1)-release. The PowerMac uses 3.2.17(1)-release.\n> > > >\n> > > > if the problem is the bash version but you can build/install a newer one that\n> > > > doesn't have this problem [...]\n> > >\n> > > My OS X 10.13.6 has Bash 3.2.57, as well, and I'm unable to reproduce\n> > > these failures, so it seems fairly unlikely that the problem Jeffrey\n> > > is seeing isn't tied to Bash.\n> >\n> > Should I read this as\n> > \".. seems fairly likely that the problem Jeffrey is seeing is tied to bash\" ?\n> >\n> > I can't reproduce it either, so my reasoning would rather be\n> > \"The problem is probably not caused by the shipped bash version\"\n> >\n> > It could be something in the environemt, that confuses our tests here.\n> >\n> > Does\n> > ./t3902-quoted.sh   -v -d\n> > give anything useful ?\n>\n> Yes, it looks like the command reveals a couple of problems.\n>\n> I'll have to look into my iconv recipe. It has not changed in a while,\n> so something else may be responsible for the failure.\n> https://github.com/noloader/Build-Scripts/blob/master/build-iconv.sh.\n>\n> I'm not sure what to do with the HEAD problems.\n>\n> $ ./t3902-quoted.sh   -v -d\n> Initialized empty Git repository in\n> /Users/jwalton/Build-Scripts/git-2.26.2/t/trash\n> directory.t3902-quoted/.git/\n> expecting success of 3902.1 'setup':\n>\n>         mkdir \"$FN\" &&\n>         for_each_name \"echo initial >\\\"\\$name\\\"\" &&\n>         git add . &&\n>         git commit -q -m Initial &&\n>\n>         for_each_name \"echo second >\\\"\\$name\\\"\" &&\n>         git commit -a -m Second &&\n>\n>         for_each_name \"echo modified >\\\"\\$name\\\"\"\n>\n>\n> fatal: iconv_open(UTF-8,UTF-8-MAC) failed, but needed:\n>     precomposed unicode is not supported.\n>     If you want to use decomposed unicode, run\n>     \"git config core.precomposeunicode false\"\n>\n\nI am quite sure, that the trouble starts here.\nIt seems as if you are building iconv yourself ?\nAnd that iconv does not include \"UTF-8-MAC\", which is a speciality\nfor Mac.\n\nAre there any special reasons to build your own iconv ?\nYou are the first one repprting this kind of issue,\nthanks for reporting it.\n\n"},{"id":"396981","messageId":"CAH8yC8mLvG-wqrws6fnXdnuoLAoDfPqgynG9MKoSnJLhPCYu+A@mail.gmail.com","threadId":"53386","inReplyTo":"20200504201944.gh3zykhil3txdwnk@tb-raspi4","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Jeffrey Walton","fromEmail":"noloader@gmail.com","sentAt":"2020-05-04T20:30:06Z","receivedAt":"2020-05-04T20:30:35Z","isPatch":false,"sender":{"key":"noloader@gmail.com","avatar":null},"body":"On Mon, May 4, 2020 at 4:19 PM Torsten Bögershausen <tboegi@web.de> wrote:\n> On Mon, May 04, 2020 at 03:20:11PM -0400, Jeffrey Walton wrote:\n> > ...\n> > > Does\n> > > ./t3902-quoted.sh   -v -d\n> > > give anything useful ?\n> >\n> > Yes, it looks like the command reveals a couple of problems.\n> >\n> > I'll have to look into my iconv recipe. It has not changed in a while,\n> > so something else may be responsible for the failure.\n> > https://github.com/noloader/Build-Scripts/blob/master/build-iconv.sh.\n> >\n> > I'm not sure what to do with the HEAD problems.\n> >\n> > $ ./t3902-quoted.sh   -v -d\n> > Initialized empty Git repository in\n> > /Users/jwalton/Build-Scripts/git-2.26.2/t/trash\n> > directory.t3902-quoted/.git/\n> > expecting success of 3902.1 'setup':\n> >\n> >         mkdir \"$FN\" &&\n> >         for_each_name \"echo initial >\\\"\\$name\\\"\" &&\n> >         git add . &&\n> >         git commit -q -m Initial &&\n> >\n> >         for_each_name \"echo second >\\\"\\$name\\\"\" &&\n> >         git commit -a -m Second &&\n> >\n> >         for_each_name \"echo modified >\\\"\\$name\\\"\"\n> >\n> >\n> > fatal: iconv_open(UTF-8,UTF-8-MAC) failed, but needed:\n> >     precomposed unicode is not supported.\n> >     If you want to use decomposed unicode, run\n> >     \"git config core.precomposeunicode false\"\n> >\n>\n> I am quite sure, that the trouble starts here.\n> It seems as if you are building iconv yourself ?\n> And that iconv does not include \"UTF-8-MAC\", which is a speciality\n> for Mac.\n\nOh, thanks. I was not aware.\n\nI'll open a bug report with the iconv folks letting them know\nconfigure has some gaps on OS X.\n\n> Are there any special reasons to build your own iconv ?\n\nYes, iconv bugs on older platforms.\n\nThe only way I've found to avoid intermittent problems on older\nplatforms is using the latest iconv (which is pretty stable nowadays),\nand avoid the glibc iconv.\n\nJeff\n"},{"id":"396995","messageId":"CAH8yC8nyg6pRStrQxkO6DzqRbLhhza0vx1U1cGUV4P4MQ3jZ7Q@mail.gmail.com","threadId":"53386","inReplyTo":"CAH8yC8mLvG-wqrws6fnXdnuoLAoDfPqgynG9MKoSnJLhPCYu+A@mail.gmail.com","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Jeffrey Walton","fromEmail":"noloader@gmail.com","sentAt":"2020-05-04T21:39:50Z","receivedAt":"2020-05-04T21:40:20Z","isPatch":false,"sender":{"key":"noloader@gmail.com","avatar":null},"body":"On Mon, May 4, 2020 at 4:30 PM Jeffrey Walton <noloader@gmail.com> wrote:\n>\n> On Mon, May 4, 2020 at 4:19 PM Torsten Bögershausen <tboegi@web.de> wrote:\n> > On Mon, May 04, 2020 at 03:20:11PM -0400, Jeffrey Walton wrote:\n> > > ...\n> > > > Does\n> > > > ./t3902-quoted.sh   -v -d\n> > > > give anything useful ?\n> > >\n> > > Yes, it looks like the command reveals a couple of problems.\n> > >\n> > > I'll have to look into my iconv recipe. It has not changed in a while,\n> > > so something else may be responsible for the failure.\n> > > https://github.com/noloader/Build-Scripts/blob/master/build-iconv.sh.\n> > >\n> > > I'm not sure what to do with the HEAD problems.\n> > >\n> > > $ ./t3902-quoted.sh   -v -d\n> > > Initialized empty Git repository in\n> > > /Users/jwalton/Build-Scripts/git-2.26.2/t/trash\n> > > directory.t3902-quoted/.git/\n> > > expecting success of 3902.1 'setup':\n> > >\n> > >         mkdir \"$FN\" &&\n> > >         for_each_name \"echo initial >\\\"\\$name\\\"\" &&\n> > >         git add . &&\n> > >         git commit -q -m Initial &&\n> > >\n> > >         for_each_name \"echo second >\\\"\\$name\\\"\" &&\n> > >         git commit -a -m Second &&\n> > >\n> > >         for_each_name \"echo modified >\\\"\\$name\\\"\"\n> > >\n> > >\n> > > fatal: iconv_open(UTF-8,UTF-8-MAC) failed, but needed:\n> > >     precomposed unicode is not supported.\n> > >     If you want to use decomposed unicode, run\n> > >     \"git config core.precomposeunicode false\"\n> > >\n> >\n> > I am quite sure, that the trouble starts here.\n> > It seems as if you are building iconv yourself ?\n> > And that iconv does not include \"UTF-8-MAC\", which is a specialty\n> > for Mac.\n>\n> Oh, thanks. I was not aware.\n>\n> I'll open a bug report with the iconv folks letting them know\n> configure has some gaps on OS X.\n\nThanks again Torsten.\n\nI am not seeing an option to enable the encoding in iConv. Would you\nhappen to know what is needed?\n\nThanks again.\n\n$ cd libiconv-1.16\n$ ./configure --help\n`configure' configures libiconv 1.16 to adapt to many kinds of systems.\n\nUsage: ./configure [OPTION]... [VAR=VALUE]...\n\nTo assign environment variables (e.g., CC, CFLAGS...), specify them as\nVAR=VALUE.  See below for descriptions of some of the useful variables.\n\nDefaults for the options are specified in brackets.\n\nConfiguration:\n  -h, --help              display this help and exit\n      --help=short        display options specific to this package\n      --help=recursive    display the short help of all the included packages\n  -V, --version           display version information and exit\n  -q, --quiet, --silent   do not print `checking ...' messages\n      --cache-file=FILE   cache test results in FILE [disabled]\n  -C, --config-cache      alias for `--cache-file=config.cache'\n  -n, --no-create         do not create output files\n      --srcdir=DIR        find the sources in DIR [configure dir or `..']\n\nInstallation directories:\n  --prefix=PREFIX         install architecture-independent files in PREFIX\n                          [/usr/local]\n  --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX\n                          [PREFIX]\n\nBy default, `make install' will install all the files in\n`/usr/local/bin', `/usr/local/lib' etc.  You can specify\nan installation prefix other than `/usr/local' using `--prefix',\nfor instance `--prefix=$HOME'.\n\nFor better control, use the options below.\n\nFine tuning of the installation directories:\n  --bindir=DIR            user executables [EPREFIX/bin]\n  --sbindir=DIR           system admin executables [EPREFIX/sbin]\n  --libexecdir=DIR        program executables [EPREFIX/libexec]\n  --sysconfdir=DIR        read-only single-machine data [PREFIX/etc]\n  --sharedstatedir=DIR    modifiable architecture-independent data [PREFIX/com]\n  --localstatedir=DIR     modifiable single-machine data [PREFIX/var]\n  --libdir=DIR            object code libraries [EPREFIX/lib]\n  --includedir=DIR        C header files [PREFIX/include]\n  --oldincludedir=DIR     C header files for non-gcc [/usr/include]\n  --datarootdir=DIR       read-only arch.-independent data root [PREFIX/share]\n  --datadir=DIR           read-only architecture-independent data [DATAROOTDIR]\n  --infodir=DIR           info documentation [DATAROOTDIR/info]\n  --localedir=DIR         locale-dependent data [DATAROOTDIR/locale]\n  --mandir=DIR            man documentation [DATAROOTDIR/man]\n  --docdir=DIR            documentation root [DATAROOTDIR/doc/libiconv]\n  --htmldir=DIR           html documentation [DOCDIR]\n  --dvidir=DIR            dvi documentation [DOCDIR]\n  --pdfdir=DIR            pdf documentation [DOCDIR]\n  --psdir=DIR             ps documentation [DOCDIR]\n\nProgram names:\n  --program-prefix=PREFIX            prepend PREFIX to installed program names\n  --program-suffix=SUFFIX            append SUFFIX to installed program names\n  --program-transform-name=PROGRAM   run sed PROGRAM on installed program names\n\nSystem types:\n  --build=BUILD     configure for building on BUILD [guessed]\n  --host=HOST       cross-compile to build programs to run on HOST [BUILD]\n\nOptional Features:\n  --disable-option-checking  ignore unrecognized --enable/--with options\n  --disable-FEATURE       do not include FEATURE (same as --enable-FEATURE=no)\n  --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]\n  --enable-silent-rules   less verbose build output (undo: \"make V=1\")\n  --disable-silent-rules  verbose build output (undo: \"make V=0\")\n  --enable-dependency-tracking\n                          do not reject slow dependency extractors\n  --disable-dependency-tracking\n                          speeds up one-time build\n  --disable-largefile     omit support for large files\n  --enable-static[=PKGS]  build static libraries [default=no]\n  --enable-shared[=PKGS]  build shared libraries [default=yes]\n  --enable-fast-install[=PKGS]\n                          optimize for fast installation [default=yes]\n  --disable-libtool-lock  avoid locking (might break parallel builds)\n  --enable-relocatable    install a package that can be moved in the file\n                          system\n  --enable-extra-encodings\n                          add support for a few rarely used encodings\n  --disable-rpath         do not hardcode runtime library paths\n  --disable-nls           do not use Native Language Support\n\nOptional Packages:\n  --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]\n  --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)\n  --with-pic[=PKGS]       try to use only PIC/non-PIC objects [default=use\n                          both]\n  --with-aix-soname=aix|svr4|both\n                          shared library versioning (aka \"SONAME\") variant to\n                          provide on AIX, [default=aix].\n  --with-gnu-ld           assume the C compiler uses GNU ld [default=no]\n  --with-sysroot[=DIR]    Search for dependent libraries within DIR (or the\n                          compiler's sysroot if not specified).\n  --with-gnu-ld           assume the C compiler uses GNU ld [default=no]\n  --with-libiconv-prefix[=DIR]  search for libiconv in DIR/include and DIR/lib\n  --without-libiconv-prefix     don't search for libiconv in\nincludedir and libdir\n  --with-libintl-prefix[=DIR]  search for libintl in DIR/include and DIR/lib\n  --without-libintl-prefix     don't search for libintl in includedir and libdir\n\nSome influential environment variables:\n  CC          C compiler command\n  CFLAGS      C compiler flags\n  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a\n              nonstandard directory <lib dir>\n  LIBS        libraries to pass to the linker, e.g. -l<library>\n  CPPFLAGS    (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if\n              you have headers in a nonstandard directory <include dir>\n  CPP         C preprocessor\n  LT_SYS_LIBRARY_PATH\n              User-defined run-time library search path.\n\nUse these variables to override the choices made by `configure' or to help\nit to find libraries and programs with nonstandard names/locations.\n"},{"id":"397045","messageId":"20200505041033.w2q7h5k7otetfrus@tb-raspi4","threadId":"53386","inReplyTo":"CAH8yC8nyg6pRStrQxkO6DzqRbLhhza0vx1U1cGUV4P4MQ3jZ7Q@mail.gmail.com","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2020-05-05T04:10:33Z","receivedAt":"2020-05-05T04:10:38Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On Mon, May 04, 2020 at 05:39:50PM -0400, Jeffrey Walton wrote:\n> On Mon, May 4, 2020 at 4:30 PM Jeffrey Walton <noloader@gmail.com> wrote:\n> >\n> > On Mon, May 4, 2020 at 4:19 PM Torsten Bögershausen <tboegi@web.de> wrote:\n> > > On Mon, May 04, 2020 at 03:20:11PM -0400, Jeffrey Walton wrote:\n> > > > ...\n> > > > > Does\n> > > > > ./t3902-quoted.sh   -v -d\n> > > > > give anything useful ?\n> > > >\n> > > > Yes, it looks like the command reveals a couple of problems.\n> > > >\n> > > > I'll have to look into my iconv recipe. It has not changed in a while,\n> > > > so something else may be responsible for the failure.\n> > > > https://github.com/noloader/Build-Scripts/blob/master/build-iconv.sh.\n> > > >\n> > > > I'm not sure what to do with the HEAD problems.\n> > > >\n> > > > $ ./t3902-quoted.sh   -v -d\n> > > > Initialized empty Git repository in\n> > > > /Users/jwalton/Build-Scripts/git-2.26.2/t/trash\n> > > > directory.t3902-quoted/.git/\n> > > > expecting success of 3902.1 'setup':\n> > > >\n> > > >         mkdir \"$FN\" &&\n> > > >         for_each_name \"echo initial >\\\"\\$name\\\"\" &&\n> > > >         git add . &&\n> > > >         git commit -q -m Initial &&\n> > > >\n> > > >         for_each_name \"echo second >\\\"\\$name\\\"\" &&\n> > > >         git commit -a -m Second &&\n> > > >\n> > > >         for_each_name \"echo modified >\\\"\\$name\\\"\"\n> > > >\n> > > >\n> > > > fatal: iconv_open(UTF-8,UTF-8-MAC) failed, but needed:\n> > > >     precomposed unicode is not supported.\n> > > >     If you want to use decomposed unicode, run\n> > > >     \"git config core.precomposeunicode false\"\n> > > >\n> > >\n> > > I am quite sure, that the trouble starts here.\n> > > It seems as if you are building iconv yourself ?\n> > > And that iconv does not include \"UTF-8-MAC\", which is a specialty\n> > > for Mac.\n> >\n> > Oh, thanks. I was not aware.\n> >\n> > I'll open a bug report with the iconv folks letting them know\n> > configure has some gaps on OS X.\n>\n> Thanks again Torsten.\n>\n> I am not seeing an option to enable the encoding in iConv. Would you\n> happen to know what is needed?\n>\n> Thanks again.\n>\n> $ cd libiconv-1.16\n> $ ./configure --help\n> `configure' configures libiconv 1.16 to adapt to many kinds of systems.\n\nHej Jeffrey,\nI am not an iconv expert - and don't intend to become one.\nThe UTF-8-MAC conversion does probably only exist in the\ncode for iconv shipped on Mac OS - so it could happen that this\ncode is not open source.\nThere may be ways to \"extract it\" :\nEither that information is part of the unicode specification,\nand there may be tables that can be converted into c-code that\nfits into the iconv code base. I don't know.\nOr you can use the iconv on MacOs itself to generate such a table.\nThat is all somewhat behind my horizon.\n\nFor Git (under MacOS) we need UTF-8-MAC to compensate for HPS,\n(or HPF+) so that all filenames with non-ASCII codepoints are\nstored in the repo in precomposed unicode.\nThis is what Linux and Windoes and Unix is using, this commit\nmay give more information about the what and why:\n\n  commit 76759c7dff53e8c84e975b88cb8245587c14c7ba\n  Author: Torsten Bögershausen <tboegi@web.de>\n  Date:   Sun Jul 8 15:50:25 2012 +0200\n    git on Mac OS and precomposed unicode\n\nBy the way, does\n./t3910-mac-os-precompose.sh\nwork on your system ?\n\nSo far I am not aware about any problems with iconv from MacOs\nbeing reported here on the list.\nWhich problems/bugs did you found in the iconv shipped with MacOs,\nespecially together with Git ?\n\n[snip]\n"},{"id":"397086","messageId":"A6880B7C-78B7-4D90-91E3-1CED85325FF2@me.com","threadId":"53386","inReplyTo":"20200505041033.w2q7h5k7otetfrus@tb-raspi4","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Philippe Blain","fromEmail":"philippe.blain@me.com","sentAt":"2020-05-05T12:26:38Z","receivedAt":"2020-05-05T12:26:44Z","isPatch":false,"sender":{"key":"philippe.blain@me.com","avatar":null},"body":"Hi everyone,\n\n> Le 5 mai 2020 à 00:10, Torsten Bögershausen <tboegi@web.de> a écrit :\n> \n> On Mon, May 04, 2020 at 05:39:50PM -0400, Jeffrey Walton wrote:\n>> On Mon, May 4, 2020 at 4:30 PM Jeffrey Walton <noloader@gmail.com> wrote:\n>>> \n>>> On Mon, May 4, 2020 at 4:19 PM Torsten Bögershausen <tboegi@web.de> wrote:\n>>>> On Mon, May 04, 2020 at 03:20:11PM -0400, Jeffrey Walton wrote:\n>>>>> ...\n>>>>>> Does\n>>>>>> ./t3902-quoted.sh   -v -d\n>>>>>> give anything useful ?\n>>>>> \n>>>>> Yes, it looks like the command reveals a couple of problems.\n>>>>> \n>>>>> fatal: iconv_open(UTF-8,UTF-8-MAC) failed, but needed:\n>>>>>    precomposed unicode is not supported.\n>>>>>    If you want to use decomposed unicode, run\n>>>>>    \"git config core.precomposeunicode false\"\n\nI also came across this error a few months ago with the \nconda-forge build of Git [1], which for the moment builds against their own\nbuild of (GNU) iconv.\n\n>>>> \n>>>> I am quite sure, that the trouble starts here.\n>>>> It seems as if you are building iconv yourself ?\n>>>> And that iconv does not include \"UTF-8-MAC\", which is a specialty\n>>>> for Mac.\n>>> \n>>> Oh, thanks. I was not aware.\n>>> \n>>> I'll open a bug report with the iconv folks letting them know\n>>> configure has some gaps on OS X.\n>> \n>> Thanks again Torsten.\n>> \n>> I am not seeing an option to enable the encoding in iConv. Would you\n>> happen to know what is needed?\n>> \n>> Thanks again.\n>> \n>> $ cd libiconv-1.16\n>> $ ./configure --help\n>> `configure' configures libiconv 1.16 to adapt to many kinds of systems.\n> \n> Hej Jeffrey,\n> I am not an iconv expert - and don't intend to become one.\n> The UTF-8-MAC conversion does probably only exist in the\n> code for iconv shipped on Mac OS - so it could happen that this\n> code is not open source.\n\nYes, this encoding only exists in the Apple fork of iconv,\nwhich is open-source (probably because of the original \nlicense); tarballs can be found at [2]. However in typical Apple fashion\nthe versioning of their iconv fork is kind of undecipherable and hard to relate to the\nupstream iconv versioning. \n\nAlso, I searched the iconv mailing list [3] when I came across this error and the consensus\nseemed to be that they do not intend to add this encoding upstream.\n\nCheers,\n\nPhilippe.\n\n[1] https://github.com/conda-forge/git-feedstock/issues/50\n[2] https://opensource.apple.com/tarballs/libiconv/\n[3] https://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=utf-8-mac&submit=Search%21&idxname=bug-gnu-libiconv&max=20&result=normal&sort=score"},{"id":"397235","messageId":"CAH8yC8nZSWSHzMiY+L4kC8OSZu9GV6H82SyvSAOqw0zX6J4xbQ@mail.gmail.com","threadId":"53386","inReplyTo":"A6880B7C-78B7-4D90-91E3-1CED85325FF2@me.com","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Jeffrey Walton","fromEmail":"noloader@gmail.com","sentAt":"2020-05-06T20:36:36Z","receivedAt":"2020-05-06T20:36:51Z","isPatch":false,"sender":{"key":"noloader@gmail.com","avatar":null},"body":"On Tue, May 5, 2020 at 8:26 AM Philippe Blain <philippe.blain@me.com> wrote:\n>  ...\n> > I am not an iconv expert - and don't intend to become one.\n> > The UTF-8-MAC conversion does probably only exist in the\n> > code for iconv shipped on Mac OS - so it could happen that this\n> > code is not open source.\n>\n> Yes, this encoding only exists in the Apple fork of iconv,\n> which is open-source (probably because of the original\n> license); tarballs can be found at [2]. However in typical Apple fashion\n> the versioning of their iconv fork is kind of undecipherable and hard to relate to the\n> upstream iconv versioning.\n>\n> Also, I searched the iconv mailing list [3] when I came across this error and the consensus\n> seemed to be that they do not intend to add this encoding upstream.\n>\n> Cheers,\n>\n> Philippe.\n>\n> [1] https://github.com/conda-forge/git-feedstock/issues/50\n> [2] https://opensource.apple.com/tarballs/libiconv/\n> [3] https://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=utf-8-mac&submit=Search%21&idxname=bug-gnu-libiconv&max=20&result=normal&sort=score\n\nThanks Phillipe.\n\nI found two sources for libiconv with UTF-8-Mac. First is a GitHub at\nhttps://github.com/fumiyas/libiconv-utf8mac. The second is the\nopensource.apple.com link you provided at [2].\n\nThe GitHub claims to be layered on top of libiconv 1.16, but I was not\nable to get a working tarball from it. It looks like Apple's\nlibiconv-59.tar.gz is the answer to this problem.\n\nThanks again for the help.\n\nJeff\n"},{"id":"397236","messageId":"CAH8yC8=YfjUqYmAs7AVtwK2MtVi-W+LfiidkwAVcy4S2TYm=4A@mail.gmail.com","threadId":"53386","inReplyTo":"20200505041033.w2q7h5k7otetfrus@tb-raspi4","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Jeffrey Walton","fromEmail":"noloader@gmail.com","sentAt":"2020-05-06T20:48:51Z","receivedAt":"2020-05-06T20:49:06Z","isPatch":false,"sender":{"key":"noloader@gmail.com","avatar":null},"body":"On Tue, May 5, 2020 at 12:10 AM Torsten Bögershausen <tboegi@web.de> wrote:\n>\n> On Mon, May 04, 2020 at 05:39:50PM -0400, Jeffrey Walton wrote:\n> > On Mon, May 4, 2020 at 4:30 PM Jeffrey Walton <noloader@gmail.com> wrote:\n> > >\n> > > ...\n> By the way, does\n> ./t3910-mac-os-precompose.sh\n> work on your system ?\n>\n> So far I am not aware about any problems with iconv from MacOs\n> being reported here on the list.\n> Which problems/bugs did you found in the iconv shipped with MacOs,\n> especially together with Git ?\n\nThanks again Torsten .\n\nSo there are several problems with libiconv. First, sometimes it is\ntoo old and carries bugs with it. For example, sed and awk fail to\nbuild and pass their self tests because they expect a minimum version\nof libiconv.\n\nSecond, there are some modern bugs that needs fixing. They were\nreported after libiconv 1.16 was released. It needs patches.\n\nThird, libiconv cannot get through testing with UBsan. It causes a\nnumber of packages to fail to configure or pass their self tests. It\nneeds patches.\n\nFourth, libiconv cannot get through testing with Asan and Valgrind. It\nleaks resources like a sieve, and leaves memory and file handles open.\nIt causes a number of packages to fail to configure or pass their self\ntests. It needs more patches.\n\nDue to all the problems with libiconv I just patch it and build it\neverywhere I need it.\n\nThe other option is to wait for the maintainers to fix libiconv. Based\non some reading about the UTF-8-Mac problem I don't think that will\nhappen. And they are not interested in fixing the resource leaks. GNU\nhas such low coding standards...\n\nJeff\n"},{"id":"397256","messageId":"CAH8yC8maYWBGgNHX8AAwVNe+dxEwpD6yXPaFd822wPmAGaUPCA@mail.gmail.com","threadId":"53386","inReplyTo":"CAH8yC8nZSWSHzMiY+L4kC8OSZu9GV6H82SyvSAOqw0zX6J4xbQ@mail.gmail.com","subject":"Re: Git 2.26.2 and failed self tests on OS X","fromName":"Jeffrey Walton","fromEmail":"noloader@gmail.com","sentAt":"2020-05-07T04:12:04Z","receivedAt":"2020-05-07T04:12:20Z","isPatch":false,"sender":{"key":"noloader@gmail.com","avatar":null},"body":"On Wed, May 6, 2020 at 4:36 PM Jeffrey Walton <noloader@gmail.com> wrote:\n>\n> On Tue, May 5, 2020 at 8:26 AM Philippe Blain <philippe.blain@me.com> wrote:\n> >  ...\n> > > I am not an iconv expert - and don't intend to become one.\n> > > The UTF-8-MAC conversion does probably only exist in the\n> > > code for iconv shipped on Mac OS - so it could happen that this\n> > > code is not open source.\n> >\n> > Yes, this encoding only exists in the Apple fork of iconv,\n> > which is open-source (probably because of the original\n> > license); tarballs can be found at [2]. However in typical Apple fashion\n> > the versioning of their iconv fork is kind of undecipherable and hard to relate to the\n> > upstream iconv versioning.\n> >\n> > Also, I searched the iconv mailing list [3] when I came across this error and the consensus\n> > seemed to be that they do not intend to add this encoding upstream.\n> >\n> > [1] https://github.com/conda-forge/git-feedstock/issues/50\n> > [2] https://opensource.apple.com/tarballs/libiconv/\n> > [3] https://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=utf-8-mac&submit=Search%21&idxname=bug-gnu-libiconv&max=20&result=normal&sort=score\n>\n> Thanks Phillipe.\n>\n> I found two sources for libiconv with UTF-8-Mac. First is a GitHub at\n> https://github.com/fumiyas/libiconv-utf8mac. The second is the\n> opensource.apple.com link you provided at [2].\n>\n> The GitHub claims to be layered on top of libiconv 1.16, but I was not\n> able to get a working tarball from it. It looks like Apple's\n> libiconv-59.tar.gz is the answer to this problem.\n\nI had to punt on Apple's port. libiconv-59.tar.gz is libiconv-1.11. It\nis too old to be useful.\n\nlibiconv-utf8mac is based on libiconv-1.16 and worked fine. It took my\npatches after I figured out the complete procedure. On the upside,\nlibiconv-utf8mac works on Linux and Solaris too. So there is support\nfor UTF-8-Mac if needed.\n\nJeff\n"}]}