fsprojects / fsprojects/Paket

Upgrading V9 to V10 causes dependency missing errors

Open
#4,324 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

It would appear this is related to changes in the paket.targets.

The error we get on build is that there are missing dependencies.

These are framework projects targetting 4.7.1.

A big difference i can see in the generated "obj" files is that in project.assets.json all dependencies are now missing.
The same is trie in the csproj.nuget.dgspec.json under the "net471" framework.

I think it's this change https://github.com/fsprojects/Paket/pull/4247

The dependencies file we have:

source https://[REDACTED]
source https://[REDACTED]
source https://[REDACTED]
strategy: min
redirects: on

nuget package1
nuget package2 ~> 1.0.0

the lock file adds restriction: >= net471 to all top level dependency lines.

the reference file has all the dependencies we reference, 99.9% of which will be 2nd level dependencies (so in the lock, but not in the dependencies file)

we use "package2" to set a standardised version of all external dependencies across multiple repository

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 by comparing paket.targets and the generated project.assets.json and csproj.nuget.dgspec.json files for the net471 framework before and after the V9-to-V10 upgrade. Review the referenced Paket change and inspect how the dependencies, lock, and reference files are interpreted. Done means framework projects restore all expected direct and transitive dependencies and build successfully.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.