Skip to content

Conversation

compnerd
Copy link
Member

@compnerd compnerd commented Sep 7, 2020

This follows the change in swiftlang/swift-package-manager#2909. Without
this change, it is not possible to build SourceKit-LSP without the local
dependencies as the version conflict prevents a resolution.

Thanks to @owenv for pointing out the change in s-p-m!

This follows the change in swiftlang/swift-package-manager#2909.  Without
this change, it is not possible to build SourceKit-LSP without the local
dependencies as the version conflict prevents a resolution.

Thanks to @owenv for pointing out the change in s-p-m!
@compnerd
Copy link
Member Author

compnerd commented Sep 7, 2020

@swift-ci please test

@MaxDesiatov
Copy link
Contributor

This would probably break #306, which I think only works with 0.3.1. @natecook1000 would you mind confirming this please? As far as I understand, the API is the same in 0.3.0 and 0.3.1 as required by semantic versioning, but a bug in 0.3.0 prevents it from working correctly?

@compnerd
Copy link
Member Author

compnerd commented Sep 7, 2020

Unfortunately, building s-p-m against s-a-p 0.3.1 fails due to an assertion triggering. Right now, it is not possible to build SK-LSP as s-p-m pins to =0.3.0 and SK pins to >=0.3.1.

@benlangmuir
Copy link
Contributor

As @MaxDesiatov said, this change is not compatible for #306. I confirmed that it crashes trying to run sourcekit-lsp. I'm reverting that change in #313 to get us back to a working configuration. We can reapply #306 when everything is ready.

@benlangmuir benlangmuir closed this Sep 8, 2020
@compnerd compnerd deleted the pinning branch September 8, 2020 18:02
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.

3 participants