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-4072] Better response rather than "unsatisfiable" #5093

swift-ci opened this issue Feb 25, 2017 · 1 comment

[SR-4072] Better response rather than "unsatisfiable" #5093

swift-ci opened this issue Feb 25, 2017 · 1 comment


Copy link

swift-ci commented Feb 25, 2017

Previous ID SR-4072
Radar rdar://problem/31022815
Original Reporter dudu (JIRA User)
Type Improvement
Status Resolved
Resolution Done
Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Improvement
Assignee None
Priority Medium

md5: c239645f7277a19c9afb2e857471a18b

is duplicated by:

  • SR-3501 Poor diagnostic when invalid version is specified
  • SR-4236 Unsatisfiable dependencies error should mention pinning
  • SR-4237 Unsatisfiable dependency error should say which dependency can't be satisfied

relates to:

  • SR-4124 Dependency resolution error for unsatisfiable dependencies due to tools version should say why
  • SR-4236 Unsatisfiable dependencies error should mention pinning

Issue Description:

When there are several dependencies declare in Package.swift. And one of them, let us call PackageA, only has one tag version 1.0.9 in git. And then in Package.swift, user uses a wrong majorversion 2. Then run "swift build". Observe the result.

Actual result:
Only return an error message "unsatisfiable".

Expected improvement:
It should return an error message with which dependency does not work out, like the version of dependency Package A could not be found. In some certain case, like package has only one version, it would be better if package manager could give some suggestions.

Copy link

aciidb0mb3r commented Apr 10, 2017

Stardust bot update:
Branch: master
Commit: 0f505fe

@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
None yet
None yet

No branches or pull requests

2 participants