NVIDIA / NVIDIA/simready-foundation
Clean source checkout cannot run documented repo.sh lifecycle
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 88
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
A clean checkout of 0ed0dfbc539c9de99289771bd6848effe3ef5779 on Linux cannot run ./repo.sh build (or any repo.sh command). repo.sh immediately executes tools/packman/python.sh tools/repoman/repoman.py, but neither tools/packman nor tools/repoman is present in the source tree, submodules, or release checkout.
Observed error:
./repo.sh: line 10: .../tools/packman/python.sh: No such file or directory
The direct validation workflow remains healthy: the sample-content regression reports no regressions against main, and simready-validate passes the bundled Sample-Profile asset.
Acceptance: either include/bootstrap the required Packman/Repoman tooling in a clean checkout, or replace/remove repo.sh and document the public build/package lifecycle that a source-only CI worker should invoke.
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
Reproduce the failure with ./repo.sh build from a clean Linux checkout, then inspect repo.sh and its references to tools/packman/python.sh and tools/repoman/repoman.py. Check the direct sample-content regression and simready-validate workflows; done means a clean source-only checkout can follow a documented build/package lifecycle without the missing tooling error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, shell
- Domain
- build-system, ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100