Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

`pod spec lint` fails with full path to JSON specs #2157

Closed
kylef opened this Issue · 2 comments

3 participants

@kylef
Owner
$ pod spec lint /Users/kylef/.cocoapods/repos/master/Specs/Calabash/0.9.168/Calabash.podspec.json

Stack

   CocoaPods : 0.33.0
        Ruby : ruby 2.0.0p451 (2014-02-24 revision 45167) [universal.x86_64-darwin13]
    RubyGems : 2.0.14
        Host : Mac OS X 10.9.2 (13C1021)
       Xcode : 5.1.1 (5B1008)
Ruby lib dir : /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @ b947340d648f51d66a6df1cbd1b5f7d8cf5a6de0

Error

Errno::ENOTDIR - Not a directory - /Users/kylef/.cocoapods/repos/master/Specs/Calabash/0.9.168/Calabash.podspec.json/Calabash.podspec
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:36:in `initialize'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:36:in `open'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:36:in `open'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/external_sources/podspec_source.rb:15:in `block in fetch'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/user_interface.rb:73:in `titled_section'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/external_sources/podspec_source.rb:13:in `fetch'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/installer/analyzer.rb:296:in `block (2 levels) in fetch_external_sources'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/installer/analyzer.rb:294:in `each'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/installer/analyzer.rb:294:in `block in fetch_external_sources'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/user_interface.rb:52:in `section'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/installer/analyzer.rb:293:in `fetch_external_sources'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/installer/analyzer.rb:56:in `analyze'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/installer.rb:176:in `analyze'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/installer.rb:98:in `block in resolve_dependencies'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/user_interface.rb:52:in `section'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/installer.rb:97:in `resolve_dependencies'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/installer.rb:89:in `install!'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/validator.rb:303:in `install_pod'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/validator.rb:209:in `block in perform_extensive_analysis'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/validator.rb:205:in `each'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/validator.rb:205:in `perform_extensive_analysis'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/validator.rb:71:in `validate'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/command/spec.rb:93:in `block in run'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/command/spec.rb:86:in `each'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/command/spec.rb:86:in `run'
/Users/kylef/gems/gems/claide-0.6.1/lib/claide/command.rb:281:in `run'
/Users/kylef/gems/gems/cocoapods-0.33.0/lib/cocoapods/command.rb:48:in `run'
/Users/kylef/gems/gems/cocoapods-0.33.0/bin/pod:33:in `<top (required)>'
/Users/kylef/gems/bin/pod:23:in `load'
/Users/kylef/gems/bin/pod:23:in `<main>'
@kylef
Owner

To directories fails too:

$ pod spec lint /Users/kylef/.cocoapods/repos/master/Specs/Calabash/0.9.168
[!] No specs found in the current directory.
@AliSoftware
Collaborator

That's strange, I got quite the opposite issue in #2147 (crash when passing a directory instead of the podspec).

Sure my issue is for pod lib lint and not pod spec lint but I believe there is some common code/logic between the two?

@fabiopelosin fabiopelosin added the label
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.