Using a local folder for NuGet packages with a NuGet API causes packages to only restore from NuGet API
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- tooling
Research direction
Reproduce the behavior with a paket.dependencies file containing a local folder source and the NuGet API, then run paket update. Trace how Paket selects a package when matching versions exist in both sources; done means the package is restored from the local folder as expected.
Written by the indexing model from the issue text.
Description
Description
I have a .Net core application with 2 package sources, a local folder on the file system and the NuGet API feed. The local folder on the file system has a modified version of Saturn with the same version number as the version of Saturn available on NuGet. Running mono .paket/paket.exe update does not take the package from the local file system
Repro steps
-
Create a folder on the local machine with a NuGet package which is also available on NuGet
-
Create a new .Net core project
-
Add a dependency to paket.dependencies which is available in the local folder as well as on NuGet
-
Add the local folder as the first source in the paket.dependencies file
-
Run paket update
Expected behavior
I'd expect Paket to use the local file system to restore the NuGet package
Actual behavior
Paket restores the package from the NuGet API feed instead
Known workarounds
No known workarounds right now
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
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.
More from fsprojects/Paket
-
agentic-workflows automation repo-assist
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
fsprojects/Paket#4411 ·
-
agentic-workflows automation repo-assist
Difficulty 1/5 Under an hour Newbie friendliness 82/100
fsprojects/Paket#4400 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
fsprojects/Paket#4255 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
fsprojects/Paket#2321 · 3 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
fsprojects/Paket#4428 ·
All issues in fsprojects/Paket
Similar issues
-
comp/cron P2 sweeper:risk-automation type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#117792 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
bancolombia/sentinel#20 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
alunduil/woodland-generators#669 ·