fsprojects / fsprojects/Paket

Using Git Repository as NuGet Source Still References Package on NuGet.org

Open
#3,960 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

Description

I know this is similar to a couple other open issues but none seemed to point to the specific case of using a git repo as a nuget source.

I've tried to follow the guide here: https://fsprojects.github.io/Paket/git-dependencies.html#Using-Git-repositories-as-NuGet-source but things are still being referenced using the nuget package that is from nuget.org instead of the one locally built by Paket using the build.cmd file from the repo.

Repro steps

Here is the build file within the repo that I want to include as a reference. It builds the nuget packages and puts them into a directory just as the example does: https://github.com/JarrodJ83/pulsar-client-dotnet/blob/develop/build.cmd

My dependencies files looks like:

git https://github.com/JarrodJ83/pulsar-client-dotnet.git develop build: "build.cmd", Packages: /pulsar-client-pkg/
nuget Pulsar.Client

run dotnet paket install

The build files run fine locally and the nuget packages are in the pulsar-client-pkg paket-files directory in the folder I expect.

Expected behavior

Expecting the Pulsar.Client NuGet reference in my lock file to point at the local repo in paket-files

NUGET
    remote: paket-files/github.com/JarrodJ83/pulsar-client-dotnet/pulsar-client-pkg
       Pulsar.Client (1.7.6)
GIT
  remote: https://github.com/JarrodJ83/pulsar-client-dotnet.git
     (db19f1a9840a93b58aecc7e2a6af99051ecd1348)
      build: build.cmd
      path: /pulsar-client-pkg/
Actual behavior

The nuget remote is still pointed to nuget.org instead of the repo.

NUGET
  remote: https://api.nuget.org/v3/index.json
    Pulsar.Client (1.7.4)
GIT
  remote: https://github.com/JarrodJ83/pulsar-client-dotnet.git
     (db19f1a9840a93b58aecc7e2a6af99051ecd1348)
      build: build.cmd
      path: /pulsar-client-pkg/
Known workarounds

No known workarounds.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue using the shown dependencies file, the referenced build.cmd, and dotnet paket install. Compare the generated lock file with the expected and actual NUGET and GIT entries. Done means the Pulsar.Client reference points to the local paket-files repository path rather than nuget.org.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp, git
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.