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?
asked by Tanvi Bhatt126 ·
What should I paste when I report an install problem?
Asked 4,310 views2 answers
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.bashsh install.sh --verbose--version-checkoutput is safe to paste in public — it is versions and paths, not tokens.answered by Daniel Oyelaranmaintainer24,177 ·Two, and they answer different questions.
bashsh install.sh --version-checkprints 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.
bashsdods doctoris 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 Nandalmaintainer41,280 ·
Have the same question?
Ask it with the command you ran and the output you got, and it will be answered here.
Ask a questionRelated
- Installing onto a machine with no outbound internet at all0 answers
- Linting only the staged feature files in a pre-commit hook — is --json stable enough?0 answers
- Unsupported architecture: i686 — is 32-bit Linux out entirely?0 answers
- har record printed no scrub line and the Cookie header is still sitting in the file0 answers
- NO_PUBKEY on apt update even though I installed the SDODS key3 answers