Skip to content

Paket pack with LOCKEDVERSION uses slightly different version #1257

Closed

Description

We are using an internal dependency called pdfcmon with a specific version 0.8.4.0. The .lock file states:

 pdfcmon (0.8.4.0)

The template file states:

 dependencies
     pdfcmon = LOCKEDVERSION

In the Nuspec it is generated as:

  <dependency id="pdfcmon" version="[0.8.4]" />

This leads to an error when installing the packages:

 Paket failed with:
 Couldn't get package details for package pdfcmon 0.8.4

Retrieving the package version 0.8.4.0 works just fine. For our internal dependencies, we use Klondike as NuGet feed. The main question is: Whose "fault" is this? Should Klondike recognize that 0.8.4.0 and [0.8.4] are the same? On the other hand: It would make sense to not omit the last zero in the spec file as it can be significant.

Activity

  1. forki commented on Nov 25, 2015

    @forki
    Member

    At the moment we write "normalized versions" into the output. Klondike
    should understand that, since it's a nuget standard. But to make things
    compatible we can probably change that and write the original version.
    On Nov 25, 2015 12:51 PM, "pdfforge" notifications@github.com wrote:

    We are using an internal dependency called pdfcmon with a specific version
    0.8.4.0. The .lock file states:

    pdfcmon (0.8.4.0)

    The template file states:

    dependencies
    pdfcmon = LOCKEDVERSION

    In the Nuspec it is generated as:

    This leads to an error when installing the packages:

    Paket failed with:
    Couldn't get package details for package pdfcmon 0.8.4

    Retrieving the package version 0.8.4.0 works just fine. For our internal
    dependencies, we use Klondike as NuGet feed. The main question is: Whose
    "fault" is this? Should Klondike recognize that 0.8.4.0 and [0.8.4] are the
    same? On the other hand: It would make sense to not omit the last zero in
    the spec file as it can be significant.

    —
    Reply to this email directly or view it on GitHub
    #1257.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions