Reactivecocoa: Installation with Carthage fails

Created on 26 Jul 2016  路  9Comments  路  Source: ReactiveCocoa/ReactiveCocoa

Since the following installation error only occurs with ReactiveCocoa, I am reporting it here.

I am trying to install v4.2.2 of ReactiveCocoa using Carthage 0.17.2.
Installing v4.2.1 works as expected, but I am unable to install v4.2.2 due to the following git error.

$ carthage update --no-use-binaries --platform iOS --use-ssh
*** Fetching Result
*** Checking out Result at "2.1.3"
*** Checking out ReactiveCocoa at "v4.2.2"
A shell task (/usr/bin/env git checkout --quiet e2cfb86c8379417c9272bb853e9f0c407167d486) failed with exit code 128:
fatal: reference is not a tree: e2cfb86c8379417c9272bb853e9f0c407167d486

$ git version
git version 2.7.4 (Apple Git-66)
bug

Most helpful comment

I had no idea RAC was pinned to my fork! 馃槄

I've just pushed Quick's current master https://github.com/Quick/Quick/commit/816489f39f590d87801ba4cd24c68e86635855de to sharplet/Quick, which includes the previously pinned commit.

All 9 comments

I can confirm I am seeing the same issue on my side.

Update: This seems to be fixed by 47bd333aac35d00acee1ff2710f42efdde33b466, so we probably need a new release.

Related to #3086

@sharplet Could you restore that commit to your fork of Quick?

@mdiep Could we make a patch release to solve this issue?

It would be better if @sharplet restored that commit鈥攂ecause then everything that's pinned to 4.2.2 will continue to work. Otherwise _everything_ needs to be updated off 4.2.2.

But if that doesn't happen, we can create a new release later today.

I had no idea RAC was pinned to my fork! 馃槄

I've just pushed Quick's current master https://github.com/Quick/Quick/commit/816489f39f590d87801ba4cd24c68e86635855de to sharplet/Quick, which includes the previously pinned commit.

@sharplet seems to be working again. 馃憤

Thank you, @sharplet! Sorry to "pin" this on you. 馃槣

I hadn't considered that pinning to someone's branch might break in the future. I'll watch this more carefully in the future!

Was this page helpful?
0 / 5 - 0 ratings