Skip to content

paket update nuget <name> should fail if package <name> was not found in dependencies or lockfile #404

Closed

Description

@agross

paket.dependencies:

source https://www.nuget.org/api/v2/

nuget Rx-Interfaces !~> 2.2

paket.lock:

NUGET
  remote: https://www.nuget.org/api/v2
  specs:
    Rx-Interfaces (2.2.2)
$ paket.exe update nuget shizzle
Paket version 0.16.1.0
found: D:\Users\agross\Downloads\t\paket.dependencies
Resolving packages:
    - exploring Rx-Interfaces 2.2.2
Locked version resolutions written to D:\Users\agross\Downloads\t\paket.lock
Rx-Interfaces 2.2.2 unzipped to D:\Users\agross\Downloads\t\packages\Rx-Interfaces
3 seconds - ready.

Activity

  1. agross commented on Nov 29, 2014

    @agross
    ContributorAuthor

    Especially, which #400 not being fixed yet, this leads to interesting situations like indirect dependencies being updated without having Paket told to so in the first place.

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