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
The only difference between the two URLs is the `.git`. On Swift 3.0.2, this causes an error in the package fetch stage. On Swift 3.1 2/15 snapshot, package fetch succeeds, but compiling stage returns errors (because the same classes are fetched twice).
If I add `.git` to the second URL, Swift 3.0.2 is able to recognize the duplicate repo and fetch correctly.
The bigger issue is that if both dependency A and B fetch dependency C, but the URLs in A and B that point to C differ in the `.git`, this causes errors even though the URLs are still technically correct.
I think we just need to implement the fix, it is a little complicated to do right now because we use the package URLs as unique keys to identify the dependencies.
We need to remove the dependency on these URLs.
We need to identify and verify that two cloned packages having different URLs but same package names are in fact equal and then do the right things.
Looks like this was marked as duplicate of SR-1195 but depending on how the fix was implemented, fixing the problem with differences in case might not fix this one (the presence or absence of a .git suffix).
Additional Detail from JIRA
md5: abab3f05ed6521ce2bf33194795e339a
duplicates:
Issue Description:
Here is a simple Package.swift that shows the issue:
The only difference between the two URLs is the `.git`. On Swift 3.0.2, this causes an error in the package fetch stage. On Swift 3.1 2/15 snapshot, package fetch succeeds, but compiling stage returns errors (because the same classes are fetched twice).
If I add `.git` to the second URL, Swift 3.0.2 is able to recognize the duplicate repo and fetch correctly.
The bigger issue is that if both dependency A and B fetch dependency C, but the URLs in A and B that point to C differ in the `.git`, this causes errors even though the URLs are still technically correct.
Issue originally identified in the public Swift@IBM Slack: https://swift-at-ibm.slack.com/archives/kitura/p1487266218001148
The text was updated successfully, but these errors were encountered: