Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-4237] Unsatisfiable dependency error should say which dependency can't be satisfied #5068

Closed
rballard opened this issue Mar 13, 2017 · 1 comment
Labels

Comments

@rballard
Copy link
Contributor

rballard commented Mar 13, 2017

Previous ID SR-4237
Radar rdar://problem/31022815
Original Reporter @rballard
Type Bug
Status Resolved
Resolution Duplicate
Environment

Apple Swift Package Manager - Swift 3.1.0 (swiftpm-12084)

Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Bug
Assignee None
Priority Medium

md5: 7ebb185655f34f4e48cd78e4d0fe24d3

duplicates:

  • SR-4072 Better response rather than "unsatisfiable"

Issue Description:

Right now if your dependencies can't be satisfied, SwiftPM just gives you an "error: unsatisfiable". That message is way too terse and should at least clearly explain that dependency requirements can't be resolved. But beyond that, it should tell you which dependency can't be satisfied, and what the conflicting requirements are, and where they come from.

Steps to reproduce:

  1. Clone vapor git@github.com:vapor/vapor.git
  2. Check out tag 2.0.0-alpha.7
  3. Run `swift build`
  4. Check out tag 1.5.9
  5. Run `swift build`
    Result: SwiftPM emits "error: unsatisfiable". This is because of the pinfile, which we should explain in SR-4236 Unsatisfiable dependencies error should mention pinning. But beyond that, this should say which dependencies are unsatisfiable.
@rballard
Copy link
Contributor Author

rballard commented Mar 13, 2017

@swift-ci create

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant