{"action":"created","issue":{"url":"https://api.github.com/repos/Carthage/Carthage/issues/868","labels_url":"https://api.github.com/repos/Carthage/Carthage/issues/868/labels{/name}","comments_url":"https://api.github.com/repos/Carthage/Carthage/issues/868/comments","events_url":"https://api.github.com/repos/Carthage/Carthage/issues/868/events","html_url":"https://github.com/Carthage/Carthage/issues/868","id":113433871,"number":868,"title":"What is the right way to specify transitive dependencies?","user":{"login":"marcpalmer","id":40849,"avatar_url":"https://avatars.githubusercontent.com/u/40849?v=3","gravatar_id":"","url":"https://api.github.com/users/marcpalmer","html_url":"https://github.com/marcpalmer","followers_url":"https://api.github.com/users/marcpalmer/followers","following_url":"https://api.github.com/users/marcpalmer/following{/other_user}","gists_url":"https://api.github.com/users/marcpalmer/gists{/gist_id}","starred_url":"https://api.github.com/users/marcpalmer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marcpalmer/subscriptions","organizations_url":"https://api.github.com/users/marcpalmer/orgs","repos_url":"https://api.github.com/users/marcpalmer/repos","events_url":"https://api.github.com/users/marcpalmer/events{/privacy}","received_events_url":"https://api.github.com/users/marcpalmer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-10-26T19:33:21Z","updated_at":"2015-10-26T21:36:46Z","closed_at":null,"body":"I'm puzzled by Carthage's dependency resolution or lack thereof. \r\n\r\nHere's my scenario:\r\n\r\nI had Carthage working, migrated all my internal libs to frameworks with their own Cartfiles, and found/forked 3rd party OSS dependencies to make them play with Carthage.\r\n\r\nMy app built, all was good, I was happy with Carthage.\r\n\r\nNow I try to build my app dependencies with Carthage and it crashes / errors (depends...) trying to fetch CocoaLumberjack branch \"swift_2.0\", because that no longer exists.\r\n\r\nObviously that is bad. Tags shouldn't go away. However the issue is more that my internal libs had to depend on that specific \"swift_2.0\" branch because CocoaLumberjack was not Swift 2 compatible on any releases.\r\n\r\n_Anyway_... now I am in a position where I have to update all of my transitive dependencies' `Cartfile` to remove the dependency on the defunct branch. This is quite onerous. It is correct of course, but it seems weird that there is apparently no way for my *project* to override the dependency with the correct one.\r\n\r\nAm I Carthaging wrong?"},"comment":{"url":"https://api.github.com/repos/Carthage/Carthage/issues/comments/151291738","html_url":"https://github.com/Carthage/Carthage/issues/868#issuecomment-151291738","issue_url":"https://api.github.com/repos/Carthage/Carthage/issues/868","id":151291738,"user":{"login":"marcpalmer","id":40849,"avatar_url":"https://avatars.githubusercontent.com/u/40849?v=3","gravatar_id":"","url":"https://api.github.com/users/marcpalmer","html_url":"https://github.com/marcpalmer","followers_url":"https://api.github.com/users/marcpalmer/followers","following_url":"https://api.github.com/users/marcpalmer/following{/other_user}","gists_url":"https://api.github.com/users/marcpalmer/gists{/gist_id}","starred_url":"https://api.github.com/users/marcpalmer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marcpalmer/subscriptions","organizations_url":"https://api.github.com/users/marcpalmer/orgs","repos_url":"https://api.github.com/users/marcpalmer/repos","events_url":"https://api.github.com/users/marcpalmer/events{/privacy}","received_events_url":"https://api.github.com/users/marcpalmer/received_events","type":"User","site_admin":false},"created_at":"2015-10-26T21:36:46Z","updated_at":"2015-10-26T21:36:46Z","body":"OK. Thanks for the detail, much appreciated. Personally I'd be in favour of a warning when updating dependencies \"Dependency X contains a tag dependency on Y with tag Z instead of a semantic version. Your builds will break if your app needs to move to a different version of Y\". That's if I've understood you correctly."}}