Dependency not satisfied after removing a folder in Pods #548

Closed
jeanregisser opened this Issue Sep 23, 2012 · 2 comments

Comments

Projects
None yet
2 participants
@jeanregisser
Contributor

jeanregisser commented Sep 23, 2012

Hi,

I came across a weird bug with subspecs / specific commit dependencies.
Basically pod install doesn't use the correct revision of a dependency after removing a directory in Pods.

I'm using CocoaPods 0.14.0.
Here's a test podfile to reproduce the issue:

platform :ios, :deployment_target => '5.0'

pod 'TestProject/SubLib', :git => 'git@github.com:jeanregisser/DummyTestProject.git'

Now if you pod install --verbose --no-clean you'll end up with libPusher checked out at pusher/libPusher@e262c4b
And this is expected since TestProject.podspec declares this specific revision.

So, now just rm -rf Pods/libPusher and again pod install --verbose --no-clean.
You'll end up with libPusher checked out at pusher/libPusher@d4d51f8 (which is the tagged version 1.3 specified in https://github.com/CocoaPods/Specs/blob/master/libPusher/1.3/libPusher.podspec) and this is wrong.

Let me know if you need more info from my setup.

@ghost ghost assigned fabiopelosin Sep 24, 2012

@jeanregisser

This comment has been minimized.

Show comment Hide comment
@jeanregisser

jeanregisser Oct 8, 2012

Contributor

This bug still exists with CocoaPods 0.15.1

Contributor

jeanregisser commented Oct 8, 2012

This bug still exists with CocoaPods 0.15.1

@fabiopelosin

This comment has been minimized.

Show comment Hide comment
@fabiopelosin

fabiopelosin Dec 17, 2012

Member

Closed by 0.17 branch.

Member

fabiopelosin commented Dec 17, 2012

Closed by 0.17 branch.

supermarin pushed a commit to supermarin/CocoaPods that referenced this issue Jan 25, 2013

[Sandbox] Clean up.
This includes a fix for an issue which caused the use of the incorrect
specification for dependencies from external sources.

Closes #548.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment