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-6389] Swift Package Manager hangs indefinitely, doesn't provide any feedback on what's gone wrong. #4916

Closed
swift-ci opened this issue Nov 15, 2017 · 0 comments
Labels

Comments

@swift-ci
Copy link
Contributor

Previous ID SR-6389
Radar None
Original Reporter KyeMaloyIBM (JIRA User)
Type Bug
Status Resolved
Resolution Duplicate

Attachment: Download

Environment

macOS 10.13.2 Beta (Build 17C76a) on a Late 2015 MacBook Pro.

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

md5: 2eb254b515b43093e3d596a4d95fa55d

duplicates:

  • SR-4400 Resolver is doing too much work

Issue Description:

When the Swift Package Manager comes into issues resolving dependencies, there is no verbose output and the process just goes on forever. This is an issue with mutliple Packages as to debug the issue, you need to go into each one and manually check its dependencies. It would make more sense for SPM to give a warning or a notice that something couldn't be resolved, and to then start searching for each individual release to try and find a match.

I have attached a Package.swift that doesn't resolve. The issue is that CloudEnvironment needs 5.0.0, which relies on Swift-cfenv 5.0.0 and above, and it also depends on SwiftMetrics which relies on Swift-cfenv 4.0.0 and above (not including 5).

If the package resolves, it is due to us having updated SwiftMetrics to use Swift-cfenv 5.0.0. To go back to the state we are in currently, set the Package.swift's SwiftMetrics to exactly 2.0.1.

@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