Skip to content

paket updates to older beta #292

Closed
Closed

Description

@agross
nuget Machine.Specifications.Should ~> 0

in lockfile:

...
    Machine.Specifications (0.8.3)
    Machine.Specifications.Should (0.7.2)
...

$ paket update updates MSpec to an older beta.

in lockfile:

...
    Machine.Specifications (0.8.3-Beta0000-0014)
    Machine.Specifications.Should (0.7.2-Beta0000-0006)
...

@forki @mexx

Activity

  1. forki commented on Oct 23, 2014

    @forki
    Member

    I assume the new semver parser doesn't flag as prerelease. The old one had
    probably ignored the double dash versions

  2. mexx commented on Oct 23, 2014

    @mexx
    Contributor

    Yes, it's the problem with numbers before dash.

  3. forki commented on Oct 23, 2014

    @forki
    Member

    Do you know how to fix it?
    On Oct 23, 2014 9:04 PM, "Max Malook" notifications@github.com wrote:

    Yes, it's the problem with numbers before dash.

    —
    Reply to this email directly or view it on GitHub
    #292 (comment).

  4. mexx commented on Oct 23, 2014

    @mexx
    Contributor

    I'm looking currently into it.

  5. mexx commented on Oct 23, 2014

    @mexx
    Contributor

    I have trouble with the number detection, which is used to correct the sorting of versions.
    When we implement SemVer v2 this extra handling would not work anymore, as pre-release parts are separated with dots, not by dashes and parts should only be sorted numeric when they consist solely of numbers.
    Current handling tries to separate a part into a name and a number, how should we proceed with this behavior?

  6. mexx commented on Oct 23, 2014

    @mexx
    Contributor

    I currently would suggest to revert #288, as it's introduced the bigger problem as it supposed to solve, and address all the things with #289.

  7. forki commented on Oct 23, 2014

    @forki
    Member

    Ok good idea.
    On Oct 23, 2014 9:40 PM, "Max Malook" notifications@github.com wrote:

    I currently would suggest to revert #288
    #288, as it's introduced the
    bigger problem as it supposed to solve, and address all the things with
    #289 #289.

    —
    Reply to this email directly or view it on GitHub
    #292 (comment).

  8. forki commented on Oct 23, 2014

    @forki
    Member

    done

  9. forki commented on Oct 23, 2014

    @forki
    Member

    Btw: big respect for such a suggestion. That's never easy.

  10. mexx commented on Oct 23, 2014

    @mexx
    Contributor

    Bug in resolution of pre-release versions is less important as a bug in resolution of normal version, so it was easy to decide. But thanks for kudos, I'm trying my best ;)

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions