Matt Diephouse

I'm seeing this today. The resolver is getting stuck during `carthage update`.

> also included github "ReactiveCocoa/ReactiveCocoa" ~> 4.2.0 but Wolox/WLXNordicUtilities included it like "ReactiveCocoa/ReactiveCocoa" ~> 4.2.0. Were those supposed to be different?

If you see this, it's because Carthage is trying to resolve your dependencies, but can't find versions that work together. It's going further back in history to try to find...

Not currently, no. You'd need to examine them manually.

@fobin You're spot on that this is related to branch pinning. It can happen with any non-release pin. Hoping to fix this soon.

Nothing to report. I haven't had time to make progress on this.

The most helpful thing would be to create a test case that exhibits the issue. `ResolverSpec` is pretty straightforward and makes this easy to do. Or an even more helpful...

You're now able to specify a list of dependencies to update/build. `carthage update Alamofire`.

@drekka That's a duplicate of #1324/#1355. It'd be a great first bug if you were interested in contributing to the project. It's on my list, but I haven't gotten around...

Yup, that's what I was thinking