paket.reference to recognizing github packages in paket.lock file
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
The paket.dependencies file is:
source https://www.nuget.org/api/v2
github fsprojects/Argu
Repro steps
- Create a F# Windows console application using VS 2015/17 Community Edition (OS: Windows 2008 R2)
- Perform
paket init - Create paket.dependencies file with the following contents:
source https://www.nuget.org/api/v2
github fsprojects/Argu
- Create paket.references file in project with contents:
Argu - Perform
paket update(orpaket install) from VS menu or commandline
Expected behavior
Argu would now exist as a reference within the project containing the aforementioned paket.reference file.
Actual behavior
The following error message is display (and is not completely represented in VS Error List when install or update is performed from VS' paket menu):
Paket failed with
-> Installation Errors :
- <...full path to project...>\paket.references uses NuGet package Argu, but it was not found in the paket.lock file in group Main.
Known workarounds
clone the projects and manually link them into your solutions...ignoring paket.
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
Reproduce the issue with the shown paket.dependencies and paket.references contents, then run paket update or paket install and inspect how the paket.references entry is matched against paket.lock. Done means the GitHub package fsprojects/Argu is recognized from paket.lock and added as a project reference without the reported installation error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100