)]}' { "commit": "daac590fc1b5dffc202efdce1f03c007fe22fcfb", "tree": "1883efb29e030f6e7054ba63c7668e347c50640a", "parents": [ "8cc50228764f2313a5506a57ddafe2e7048f3b80" ], "author": { "name": "Antoine Musso", "email": "hashar@free.fr", "time": "Thu Sep 08 15:56:06 2022 +0200" }, "committer": { "name": "Antoine Musso", "email": "hashar@free.fr", "time": "Thu Sep 08 16:03:07 2022 +0200" }, "message": "doc: build rules requires /usr/bin/python\n\nmaven_jar would fail to fetch material when a `python` executable is not\nfound in path. It looks it up with:\n\n python \u003d ctx.which(\"python\")\n\nSince Debian 11 and Ubuntu 20.04 LTS, there is no more a\n`/usr/bin/python` to get rid of the ambiguity between python 2 and\npython 3.\n\n8cc50228 erroneously mentionned the build rule requires python 2,\ninstead of the lack of `python`. Adjust the document to instruct people\nto install Python 3.\n\nChange-Id: I455edc28f1b67663409ee1c612edd21a5cc57720\n", "tree_diff": [ { "type": "modify", "old_id": "82fedb09d964b0368dc61d26df3d8713352a9379", "old_mode": 33188, "old_path": "Documentation/developer-guide.md", "new_id": "70b050ecbf11d9c7d5f0a42444f66c1f24bf84bc", "new_mode": 33188, "new_path": "Documentation/developer-guide.md" } ] }