as of now swiftpm cannot handle such collisions, there has been some discussions about handling such cases on mailing list.

Perhaps we can get some context here so that we can be sure about our solutions.

Are these forks? Or completely different packages with the same name?

These are forks... maybe it is possible to allow automatic reconciliation of this when SwiftPM can pick an appropriate tag that exists and is equal in both versions?

^ sounds good to me

@ddunbar nice idea.

Certainly we could do that, and maybe we should.

However someone made a fork for a reason, a bug fix perhaps, or a feature addition. Really the end-user should pick one, and hopefully they will have compatible API (it's likely).

Whatever: we need a proper proposal.

I ran into this recently as well. We need to:

1. have better equality comparison of repository URLs (for cases in which the same repo is accessed via `https` as well as `git` etc)

2. have some way to deal with references to two different repositories that are really forks of the same one; perhaps we can use SHA comparisons for this etc

I think we shouldn't automatically merge the forks. We do plan to do a fork support feature at some point, I'll dupe this report to that bug.