From 2b0dd7355da715821ba437cb09c3b321e3aea530 Mon Sep 17 00:00:00 2001 From: Ivan Pozdeev Date: Sat, 14 Jan 2023 02:24:47 +0300 Subject: [PATCH] Specify additional required information for build failures --- .github/ISSUE_TEMPLATE.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md index bcc909e6..4097601a 100644 --- a/.github/ISSUE_TEMPLATE.md +++ b/.github/ISSUE_TEMPLATE.md @@ -19,3 +19,8 @@ Make sure you have checked all steps below. - [ ] C Compiler information (e.g. gcc 7.3): - [ ] Please attach the debug trace of the failing command as a gist: * Run `env PYENV_DEBUG=1 2>&1 | tee trace.log` and attach `trace.log`. E.g. if you have a problem with installing Python, run `env PYENV_DEBUG=1 pyenv install -v 2>&1 | tee trace.log` (note the `-v` option to `pyenv install`). +- [ ] If you have a problem with installing Python, please also attach `config.log` from the build directory + * The build directory is reported after the "BUILD FAILED" message and is usually under `/tmp`. +- [ ] If the build succeeds but the problem is still with the build process (e.g. the resulting Python is missing a feature), please attach + * the debug trace from reinstalling the faulty version with `env PYENV_DEBUG=1 pyenv install -f -k -v 2>&1 | tee trace.log` + * `config.log` from the build directory. When using `pyenv install` with `-k` as per above, the build directory will be under `$PYENV_ROOT/sources`.