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
In a recent update to SwiftPM we improved the validation of dependencies with different URLs. Specifically, we now check more accurately when two packages are named similarly but have different source git URLs. We originally made this into an error since it can yield undefined behavior, but later relaxed it to a warning since the Kitura project suffers from this setup which showed up in our source compatibility test suite: https://bugs.swift.org/browse/SR-15146
For Kitura specifically, there seems to be a mix of URLs from the original IBM GitHub organization and the current Kitura GitHub organization, which I assume stems from the fact the repos were moved from one org to the other but the dependencies on various Package.swift files still point to the IBM org. While in this case the repos are literally the same (redirect at GitHub level), SwiftPM has no way to reconcile the URL differences as it operates at the git level and cannot be aware of Github logic / redirects, and different URLs could also mean totally different sources.
To resolve this, please update all Package.swift files to use the Kitura org URLs.
Hi folks,
In a recent update to SwiftPM we improved the validation of dependencies with different URLs. Specifically, we now check more accurately when two packages are named similarly but have different source git URLs. We originally made this into an error since it can yield undefined behavior, but later relaxed it to a warning since the Kitura project suffers from this setup which showed up in our source compatibility test suite: https://bugs.swift.org/browse/SR-15146
For Kitura specifically, there seems to be a mix of URLs from the original IBM GitHub organization and the current Kitura GitHub organization, which I assume stems from the fact the repos were moved from one org to the other but the dependencies on various Package.swift files still point to the IBM org. While in this case the repos are literally the same (redirect at GitHub level), SwiftPM has no way to reconcile the URL differences as it operates at the git level and cannot be aware of Github logic / redirects, and different URLs could also mean totally different sources.
To resolve this, please update all Package.swift files to use the Kitura org URLs.
Feel free to reach out with any questions.
--Tom
cc @abertelrud @neonichu
The text was updated successfully, but these errors were encountered: