Skip to content

Specified custom repo, but still original one used #818

Closed
sirnicolaz opened this Issue Feb 26, 2013 · 6 comments

3 participants

@sirnicolaz

Hi!

I'm using Cocopods gem v 0.16.4, with ruby ruby-1.9.3-p194.

Following the documentation, I tried to setup a dependency to point to a fork of mine

pod 'SVProgressHUD', :git => 'git://github.com/sirnicolaz/SVProgressHUD'

For some reason, there is no way I can get the right source. When I run 'pod install', I just get the original repo source code.

I honestly have no idea what I am doing wrong. Any suggestion? Did I get it right that just by specifying a custom repo it should get the source from that one?

@alloy
CocoaPods member
alloy commented Feb 27, 2013

I’m guessing this has to do with the contents of Podfile.lock, which probably points to the original source and the fact that the Podfile now points to a custom source is being ignored. Can you remove it from there and try again?

@fabiopelosin
CocoaPods member

@sirnicolaz To resolve the issue we need to inspect the contents of the Podfile and the Podfile.lock. Also the verbose output of pod install would be helpful.

@sirnicolaz

Alloy's guess was correct. It was a problem with the Podfile.lock, because earlier I installed the same library from the original source apparently.

Now it works, thank you very much for the prompt support!

@sirnicolaz sirnicolaz closed this Feb 27, 2013
@alloy
CocoaPods member
alloy commented Feb 27, 2013

Good to hear. I’ll re-open the ticket, though, because it something that still has to be done.

@alloy alloy reopened this Feb 27, 2013
@fabiopelosin
CocoaPods member

We need to check that this issue is still present on 0.17

@fabiopelosin
CocoaPods member

After a quick test I've verified that adding the external source correctly triggers the reinstallation in 0.17.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.