Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[SR-6392] Dependency resolution conflict only shows one dependency #4915

Open
swift-ci opened this issue Nov 15, 2017 · 5 comments
Open

[SR-6392] Dependency resolution conflict only shows one dependency #4915

swift-ci opened this issue Nov 15, 2017 · 5 comments
Labels
bug

Comments

@swift-ci
Copy link
Contributor

Previous ID SR-6392
Radar rdar://problem/40206348
Original Reporter charliecrisp (JIRA User)
Type Bug

Attachment: Download

Environment

macOS High Sierra, using Docker with docker-compose. In this case, the Kitura and Kitura-CredentialsHTTP dependencies could not be resolved.

Additional Detail from JIRA
Votes 1
Component/s Package Manager
Labels Bug
Assignee None
Priority Medium

md5: 224dea18ac952c4f30acacc668d17dda

Issue Description:

When there are conflicting dependencies in `Package.swift`, `swift build` will give the following error, which only gives one of the conflicting dependencies.

error: dependency graph is unresolvable; found these conflicting requirements:
Dependencies:
 https://github.com/IBM-Swift/Kitura.git @ 1.7.9..<1.8.0
@abertelrud
Copy link
Contributor

This reproduces outside of Docker as well. And in fact, this looks like a known limitation of the current package dependency resolution machinery: the “transitive incompatible dependency” section of the `testDiagnostics()` unit test in the `DependencyResolverTests.swift` source file asserts that there is one dependency reported in the diagnostic, even though two different versions are involved.

This seems non-trivial to fix, so this probably comes down to a need to improve the diagnostic output of dependency resolution rather than a fix for a specific bug in the code.

@gwynne
Copy link

gwynne commented Feb 14, 2018

Also running into this. Would love to see a fix.

@swift-ci
Copy link
Contributor Author

Comment by mark wang (JIRA)

i also running into this. would love to see a fix.

@ankitspd
Copy link
Member

@swift-ci create

@swift-ci
Copy link
Contributor Author

Comment by Tabor Kelly (JIRA)

                        /^\
           /         (/^\)     /
      \   ( \         \ /     ( \     /^\
     / )   \ |        _|_      \ |   |/^\|
    | /    _|_        | |      _|_    \ /
    _|_    | |        | |      | |    _|_
    | |    | |        | |      | |    | |
    | |    | |    ****| |******| |    | |
    | |****| |****    | |      | |****| |
   *| |    | |                 | |    | |*****
 *  | |   H  A  P  P  Y               | |      *
*                                               *
| *            B  I  R  T  H  D  A  Y  !      * |
|  *****                                 *****  |
|@      **********             **********      @|
| @   @           *************           @   @ |
|  @@@ @    @                       @    @ @@@  |
|       @@@@ @      @       @      @ @@@@       |
 *            @@@@@@ @     @ @@@@@@            *
  *                   @@@@@                   *
   *****                                 *****
        **********             **********
                  *************

It would be great to get this bug fixed.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@tomerd @gwynne @ankitspd @swift-ci @abertelrud