You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Attachment: Download
Environment
macOS 10.13.2 Beta (Build 17C76a) on a Late 2015 MacBook Pro.
Additional Detail from JIRA
md5: 2eb254b515b43093e3d596a4d95fa55d
duplicates:
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.
The text was updated successfully, but these errors were encountered: