What should I paste when I report an install problem?

Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.

I keep getting asked follow-up questions when I report installer trouble and I would rather include the right thing the first time. Is there one command whose output covers it?

install cli

asked by Tanvi Bhatt

2 answers

Accepted answer
Both of those, plus the third thing people leave out: the command you actually ran, in full, and the error verbatim rather than paraphrased.
If the failure is in the middle of a long step, re-run with --verbose. Output is hidden by default and only the tail is printed on failure, so the interesting line is often in the part you did not see.
bash
```
sh install.sh --verbose
```
--version-check output is safe to paste in public — it is versions and paths, not tokens.
answered by Daniel OyelaranSDODS team
Two, and they answer different questions.
bash
```
sh install.sh --version-check
```
prints the platform, the tool versions it detected and every path it resolved, then exits without installing. That is the state of the machine before anything happens.
bash
```
sdods doctor
```
is the state after: the runner, the browser engines, the projects it can discover, the resolved variables and the database. It keeps going past a failure rather than stopping at the first one, so you get the whole picture in one pass.
answered by Reeta NandalSDODS team

Know the answer?

Wrap commands and output in triple backticks and they will render as a code block.

Checking whether you’re signed in…

Have a different question? Ask it.

What should I paste when I report an install problem?

2 answers

Know the answer?

Related