Nuget package generated by git dependency is not included.
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
I created a very minimal project to test the git dependency feature, but I feel like it's broken.
This is my very basic paket.dependencies:
source https://api.nuget.org/v3/index.json
storage: none
git https://github.com/CompositionalIT/farmer.git container-app-probes build: "dotnet pack -c Release -o PackOutput", OS: windows, Packages: PackOutput
This does clone the repository into paket-files/github.com folder, and creates a nupkg:
but then paket claims that the package is not available:
Installing into projects:
Created dependency graph (0 packages in total)
F# project C:\Users\JoostKaptein\code\disposable\repro-paket-git\repro-paket-git.fsproj does not reference FSharp.Core.
Total time taken: 5 milliseconds
Paket failed with
-> Installation Errors :
- C:\Users\JoostKaptein\code\disposable\repro-paket-git\paket.references uses NuGet package Farmer, but it was not found in the paket.lock file in group Main.
reproduction repo is available here
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 reproduction repository and inspect paket.dependencies, paket.references, and paket.lock; verify how the git dependency's PackOutput nupkg is represented during installation. Trace the dependency-resolution or installation path that reports Farmer as missing, and consider the work done when the generated package is included in the lock file and can be installed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp, git
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100