bug: cargo doesn't know how to resolve dependencies for print-rcdom
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 288
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 8
Description
See #476
If you use "*" for the dependency version, cargo cannot resolve the versions correctly:
[dependencies]
html5ever = "*"
markup5ever_rcdom = "*"
Fix: use exact dependencies
[dependencies]
html5ever = "0.25.2"
markup5ever_rcdom = "0.1.0"
Not sure if this is a bug in how the versions have been published, or a bug in cargo itself.
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 by reproducing the dependency resolution failure with the Cargo.toml snippets in the issue, then inspect the published versions of html5ever and markup5ever_rcdom. Determine whether the failure comes from their published dependency metadata or Cargo itself; the work is done when wildcard dependencies resolve correctly or the responsible component is clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100