Skip to content

Selective update shows better error message on conflict - #980

Merged
forki merged 1 commit into
fsprojects:masterfrom
mrinaldi:improve_conflict_error_message
Aug 13, 2015
Merged

Selective update shows better error message on conflict#980
forki merged 1 commit into
fsprojects:masterfrom
mrinaldi:improve_conflict_error_message

Conversation

@mrinaldi

Copy link
Copy Markdown
Contributor

When I'm updating a single package, the conflict message would not show the other packages requirements that has conflicted.

paket.dependencies:

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

nuget Ninject.Extensions.Interception
nuget Ninject.Extensions.Logging.Log4Net

paket.lock:

NUGET
  remote: https://nuget.org/api/v2
  specs:
    log4net (2.0.3)
    Ninject (2.2.1.4)
    Ninject.Extensions.Interception (2.2.1.2)
      Ninject (>= 2.2.0.0 < 2.3.0.0)
    Ninject.Extensions.Logging (2.2.0.4)
      Ninject (>= 2.2.0.0 < 2.3.0.0)
    Ninject.Extensions.Logging.Log4net (2.2.0.4)
      Ninject.Extensions.Logging (>= 2.2.0.0 < 2.3.0.0)
      log4net (>= 1.0.4)

paket update nuget Ninject.Extensions.Logging.Log4Net version 3.0.1
Outputs:

  Could not resolve package Ninject:
   - Ninject.Extensions.Logging 3.0.1 requested >= 3.0.0.0 < 3.1.0.0

This PR changes to output message to include what other packages have conflicted:

  Could not resolve package Ninject:
   - Ninject.Extensions.Interception 2.2.1.2 requested >= 2.2.0.0 < 2.3.0.0
   - Ninject.Extensions.Logging 3.0.1 requested >= 3.0.0.0 < 3.1.0.0

@forki

forki commented Aug 13, 2015

Copy link
Copy Markdown
Member

Very cool. Love it

forki added a commit that referenced this pull request Aug 13, 2015
Selective update shows better error message on conflict
@forki
forki merged commit 9ecce65 into fsprojects:master Aug 13, 2015
@mrinaldi
mrinaldi deleted the improve_conflict_error_message branch August 13, 2015 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants