Build failure on referenced unlisted minimum-version-dependencies
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
I used Paket and Fake out-of-box, via project scaffold.
I added a dependency to Owin (v.1.0.0) and Paket generated it to my NuGet package as follows:
Owin (>= 1.0.0-prerelease && <= 1.0.0)
And everything worked fine and everyone was happy. Until one day, the Owin-team unlisted the prerelease-version of the package from NuGet. Now my users started to get build errors.
This is probably a problem of NuGet-protocol in general, but as we know, they are not an open-source project accepting pull-requests. * Meanwhile Paket is the default .NET-solution to tackle NuGet-problems.
I use the following configuration:
paket.template:
dependencies
Owin 1.0.0 ~> LOCKEDVERSION
paket.lock:
Owin (1.0)
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
Reproduce the problem from the project scaffold using the shown paket.template and paket.lock entries for Owin 1.0.0, then trace Paket's NuGet dependency resolution and lock-file handling. Done means generated package dependencies no longer require an unlisted prerelease minimum version and downstream users can 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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100