`spack install --yes-to-all` does not allow forcing the fetch of a missing source
Open
Nobody has claimed this yet.
bug
impact-low
- Dominant language
- Python
- Stars
- 5.1k
- Forks
- 2.5k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 82
Description
Steps to reproduce
spack (develop=)$ spack install --yes-to-all xz@5.2.6
==> Warning: Missing a source id for xz@5.2.6
==> Installing xz-5.2.6-s632h2yx4p5qcpg7xeyekq7xh6jib3zy
==> No binary for xz-5.2.6-s632h2yx4p5qcpg7xeyekq7xh6jib3zy found: installing from source
==> Warning: There is no checksum on file to fetch xz@5.2.6 safely.
==> Fetch anyway? [y/N]
Error message
Would expect to not require confirmation.
Information on your system
- Spack: 0.17.1-1394-e6dcd382ee
- Python: 3.7.3
- Platform: linux-debian10-skylake
- Concretizer: clingo
General information
- I have run
spack debug reportand reported the version of Spack/Python/Platform - I have searched the issues of this repo and believe this is not a duplicate
- I have run the failing commands in debug mode and reported the output
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported spack install --yes-to-all xz@5.2.6 command and trace the CLI path that handles fetching a source without a checksum. Verify that --yes-to-all completes this case without an interactive confirmation, while preserving the safety warning behavior for other fetches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100