error running pod install in 0.34.4

[ydnar]

Report

• What did you do?
  I ran pod install.
• What did you expect to happen?
  Have pods installed.
• What happened instead?
  Blew up in Ruby land.

Stack

   CocoaPods : 0.34.4
        Ruby : ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin13.0]
    RubyGems : 2.2.2
        Host : Mac OS X 10.10 (14A388a)
       Xcode : 6.1 (6A1042b)
         Git : git version 1.8.5.5
Ruby lib dir : /Users/ydnar/.rbenv/versions/2.1.2/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @ e4fbbaa7c9a02133d9eaf9126f7ed0b2b7ddb14a
               master-1 - https://github.com/CocoaPods/Specs.git @ e4fbbaa7c9a02133d9eaf9126f7ed0b2b7ddb14a

Plugins

cocoapods-plugins : 0.3.1
cocoapods-trunk   : 0.3.1
cocoapods-try     : 0.4.1

Podfile

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '7.0'

link_with 'Domainr', 'DomainrTests'
pod 'PBWebViewController'
pod 'UIColor+Hex', '~> 1.0'
pod 'FlurrySDK', '~> 5.4'

Error

NoMethodError - undefined method `name' for nil:NilClass
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/installer/analyzer.rb:172:in `block (2 levels) in update_repositories_if_needed'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/installer/analyzer.rb:172:in `each'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/installer/analyzer.rb:172:in `block in update_repositories_if_needed'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/user_interface.rb:49:in `section'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/installer/analyzer.rb:171:in `update_repositories_if_needed'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/installer/analyzer.rb:48:in `analyze'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/installer.rb:184:in `analyze'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/installer.rb:106:in `block in resolve_dependencies'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/user_interface.rb:49:in `section'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/installer.rb:105:in `resolve_dependencies'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/installer.rb:90:in `install!'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/command/project.rb:71:in `run_install_with_update'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/command/project.rb:101:in `run'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/claide-0.7.0/lib/claide/command.rb:271:in `run'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/lib/cocoapods/command.rb:50:in `run'
/Users/ydnar/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/cocoapods-0.34.4/bin/pod:33:in `<top (required)>'
/Users/ydnar/.rbenv/versions/2.1.2/bin/pod:23:in `load'
/Users/ydnar/.rbenv/versions/2.1.2/bin/pod:23:in `<main>'

[alloy]

This look similar as a previous report, can you perform these steps and report back? #2625 (comment)

[ydnar]

Deleting this line from the top of Podfile sort of fixes it:
source 'https://github.com/CocoaPods/Specs.git'

But changing to a git URL really fixes it:
source 'git@github.com:CocoaPods/Specs.git'

[orta]

Perhaps relevant, both issues have two master repos:

Repositories : master - https://github.com/CocoaPods/Specs.git @ e4fbbaa7c9a02133d9eaf9126f7ed0b2b7ddb14a
               master-1 - https://github.com/CocoaPods/Specs.git @ e4fbbaa7c9a02133d9eaf9126f7ed0b2b7ddb14a

[segiddins]

A change might be needed at https://github.com/CocoaPods/CocoaPods/blob/resolver/lib/cocoapods/sources_manager.rb#L53 to ensure an exception is raised whenever source would be nil by the end of the method.

[alloy]

@orta Yeah, but I think that that is caused by the fact that apparently the source implementation is unable to detect the existing clone and thus creates a new clone. I.e. it’s related in the same way to the resolver not being able to get the source belonging to the specified URL.

[alloy]

@ydnar Interesting. For the sake of getting to the bottom of this, could you please revert to using the https one and apply the changes to source_with_url as I had asked in #2625 (comment) and report back with the output?

[alloy]

@ydnar And could you also see what the output is of:

$ cd ~/.cocoapods/repos/master
$ irb
irb(main):001:0> `git ls-remote --get-url`
=> "https://github.com/CocoaPods/Specs.git\n"
irb(main):002:0> $?.success?
=> true

[alloy]

Closing in favour of #2724.

@ydnar It would still be very much appreciated if you can help us in determining the cause, though.

[ydnar]

Sorry, was on the other side of the world getting married. Did you resolve the issue?

[alloy]

@ydnar Congrats! It would be nice if you can confirm that the issue in your case is also that you are using the git config that I described here: #2724 (comment)

[alloy]

(That issue is fixed in the current 0.35 RC1 release.)