fsprojects / fsprojects/Paket

Question about Normalized Version Numbers and third party Nuget server (ProGet)

Open
#1,777 33 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

paket does not search for 4-digit version numbers when a 3-digit version number is specified. Is this the expected behavior?

Repro steps

Steps to reproduce the problem:

  1. I a package, SqlTableDependency: 4.1.1, and uploaded it to a ProGet server.

  2. ProGet automatically appends .0 to make it a 4-digit version 4.1.1.0. (They said this is to comply with NuGet version 3.4 change for normalized version numbers: http://docs.nuget.org/Create/Versioning#Normalized_Version_Numbers.)

  3. I run paket update and it I get this error message

    Could not resolve package SqlTableDependency:

    • Dependencies file requested package SqlTableDependency: 4.1.1
    • Available versions:
      • (4.1.1.0, [https:///nuget/])
Expected behavior

I was expecting 4.1.1 to work (not realizing that ProGet was changing it to 4.1.1.0).

Actual behavior

Specifying 4.1.1 fails to find 4.1.1.0 for the package.

Known workarounds

It works when I specify 4.1.1.0. (Is this the proper way to do it?)

Related information
  • paket version 3.4.0 (or 3.4.0.0)
  • possibly related ticket: #1239

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 reviewing Paket's NuGet package version resolution using the supplied ProGet reproduction and compare it with related issue #1239. Done should establish whether a requested 3-part version matches an available 4-part normalized version and document or correct the resulting behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.