fsprojects / fsprojects/Paket

The package is downloaded from not desired repository

Open
#2,890 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

The package is downloaded from not desired repository because it exists in two specified.

Repro steps

paket.dependencies

source https://www.nuget.org/api/v2
nuget Invoke-Build

source https://www.powershellgallery.com/api/v2
nuget SplitPipeline

The package SplitPipeline exists in both www.nuget.org and www.powershellgallery.com.
It it is the same tool but the packages are slightly different due to the different nature
and purpose of repositories.

The intent of the above paket.dependencies is to get one package from nuget and another
from powershellgallery. But both packages are installed from nuget.

Is this expected? If yes, is there a reliable way to get the second package
SplitPipeline from the exact repository?

NB: How to distinguish SplitPipeline packages:

  • nuget package keeps all stuff in the subdirectory tools
  • powershellgallery package keeps its files in the root directory
Expected behavior

(not necessarily, "expected", the current is probably by design)

SplitPipeline is installed from powershellgallery

Actual behavior

SplitPipeline is installed from nuget

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

Start with the paket.dependencies example and reproduce resolution when SplitPipeline exists in both listed repositories. Trace how Paket selects the source for each package and compare the installed layouts described in the issue. Done means the requested repository can be selected reliably, or the limitation and supported configuration are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp, powershell
Domain
cli, 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.