paket why: "impossible" when lock not in sync with paket.dependencies
Open
Nobody has claimed this yet.
bug
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
paket why fails with "impossible" when asking for a top-level dependency which has just been removed from paket.dependencies, but not from paket.lock (lock is not in sync)
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 at the paket why command and reproduce the failure using a top-level dependency removed from paket.dependencies while it remains in paket.lock. Trace how the command handles this out-of-sync state and identify the relevant tests or entry points; done means the behavior is covered for this scenario and no longer reports the unexplained impossible result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100