rust-embedded / rust-embedded/meta-rust-bin
Private crates are not supported even with `net.git-fetch-with-cli = true`
Open
Nobody has claimed this yet.
- Dominant language
- BitBake
- Stars
- 124
- Forks
- 92
- Avg merge
- 6h 54m
- Merged PRs (30d)
- 2
Description
.cargo/config.toml:
[net]
git-fetch-with-cli = true
However, when compiling with bitbake, it cannot find the private crates.
| Caused by:
| failed to load source for dependency `rust-protobufs`
|
| Caused by:
| Unable to update https://abc.com/git/rust-protobufs.git?branch=main#a27c537d
|
| Caused by:
| failed to clone into: /home/ubuntu/build/tmp/work/cortexa9t2hf-neon-poky-linux-gnueabi/program/1.0+gitAUTOINC+6a7aae1cbf-r0/cargo_home/git/db/rust-protobufs-de8201c5bac7b8be
|
| Caused by:
| failed to authenticate when downloading repository
|
| * attempted to find username/password via git's `credential.helper` support, but failed
|
| if the git CLI succeeds then `net.git-fetch-with-cli` may help here
| https://doc.rust-lang.org/cargo/reference/config.html#netgit-fetch-with-cli
|
| Caused by:
| failed to acquire username/password from local configuration
| WARNING: exit code 101 from a shell command.
What is the workaround for this?
Contributor guide
No contributing guide indexed for this repository
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 with the .cargo/config.toml settings shown in the report and reproduce the failure during the BitBake compile step. Inspect how private rust-protobufs Git dependencies are fetched and how Git credential helpers are reached. Done means the issue has a verified workaround or support fix for authenticated private crates with net.git-fetch-with-cli = true.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- build-system, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100