I am having a problem with installation of Openshift origin. I tried the installation
Openshift origin 3.0 on CentOS6.5 by using below command and I got succeeded at 2 weeks ago.
sh <(curl -s https://install.openshift.com/) -w origin_deploy
But now, it says an error message that I don't know how to fix it.
Validating deployment configuration... /tmp/oo-install-20140725-1501/lib/installer/deployment.rb:328:in `are_accounts_valid?': undefined local variable or method `host' for #<Installer::Deployment:0x7f2ee4552048> (NameError)
from /tmp/oo-install-20140725-1501/lib/installer/deployment.rb:319:in `each'
from /tmp/oo-install-20140725-1501/lib/installer/deployment.rb:319:in `are_accounts_valid?'
from /tmp/oo-install-20140725-1501/lib/installer/deployment.rb:316:in `each'
from /tmp/oo-install-20140725-1501/lib/installer/deployment.rb:316:in `are_accounts_valid?'
from /tmp/oo-install-20140725-1501/lib/installer/deployment.rb:307:in `is_valid?'
from /tmp/oo-install-20140725-1501/lib/installer/assistant.rb:58:in `run'
from /tmp/oo-install-20140725-1501/bin/oo-install:187
from /tmp/oo-install-20140725-1501/bin/oo-install:185:in `loop'
from /tmp/oo-install-20140725-1501/bin/oo-install:185
Please give me some advise to solve this issue. I guess that they have released new version during 2 weeks.
Related
I am struggling a lot with this. And I know that the answer is staring me in the face somewhere but no matter what I search or look up and try, nothing works.
My schemes are all pointing to my pod frameworks and I cannot select the project target, even if I try and add a new scheme or edit an old one.
My project navigator starts with a folder as shown above, and I have NO idea how to revert back to whatever I had done to get it like this.
If anyone has any suggestions please help.
I cannot access target build settings or project build settings, Is there a way to access them without going through the project navigator ?
I cannot build properly as shown from the schemes, is there an easy fix to this ? Have I somehow changed the target path to an incorrect file location? How to revert back ?
I'm stuck :(
UPDATE:
deleting the .xcworkspace file and reinstalling the podfile gives below error code.
```
RuntimeError - [Xcodeproj] Unknown object version.
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/xcodeproj-1.5.8/lib/xcodeproj/project.rb:218:in `initialize_from_file'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/xcodeproj-1.5.8/lib/xcodeproj/project.rb:103:in `open'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/installer/analyzer.rb:918:in `block (2 levels) in inspect_targets_to_integrate'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/installer/analyzer.rb:917:in `each'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/installer/analyzer.rb:917:in `block in inspect_targets_to_integrate'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/user_interface.rb:64:in `section'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/installer/analyzer.rb:912:in `inspect_targets_to_integrate'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/installer/analyzer.rb:78:in `analyze'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/installer.rb:243:in `analyze'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/installer.rb:154:in `block in resolve_dependencies'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/user_interface.rb:64:in `section'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/installer.rb:153:in `resolve_dependencies'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/installer.rb:116:in `install!'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/command/install.rb:41:in `run'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/claide-1.0.2/lib/claide/command.rb:334:in `run'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/lib/cocoapods/command.rb:52:in `run'
/Applications/CocoaPods.app/Contents/Resources/bundle/lib/ruby/gems/2.2.0/gems/cocoapods-1.5.2/bin/pod:55:in `<top (required)>'
/Applications/CocoaPods.app/Contents/Resources/bundle/bin/pod:22:in `load'
/Applications/CocoaPods.app/Contents/Resources/bundle/bin/pod:22:in `<main>'
```
――― TEMPLATE END ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
[!] Oh no, an error occurred.
Search for existing GitHub issues similar to yours:
https://github.com/CocoaPods/CocoaPods/search?q=%5BXcodeproj%5D+Unknown+object+version.&type=Issues
If none exists, create a ticket, with the template displayed above, on:
https://github.com/CocoaPods/CocoaPods/issues/new
Be sure to first read the contributing guide for details on how to properly submit a ticket:
https://github.com/CocoaPods/CocoaPods/blob/master/CONTRIBUTING.md
Don't forget to anonymize any private data!
Looking for related issues on cocoapods/cocoapods...
- RuntimeError - [Xcodeproj] Unknown object version.
https://github.com/CocoaPods/CocoaPods/issues/6992 [closed] [16 comments]
31 Jan 2019
- - ERROR | [iOS] unknown: Encountered an unknown error (Malformed version number string ) during validation.
https://github.com/CocoaPods/CocoaPods/issues/8240 [closed] [16 comments]
12 hours ago
- Xcodeproj doesn't know about the following attributes {"inputFileListPaths"=>[], "outputFileListPaths"=>[]} for the 'PBXShellScriptBuildPhase' isa
https://github.com/CocoaPods/CocoaPods/issues/7835 [closed] [46 comments]
2 hours ago
and 44 more at:
https://github.com/cocoapods/cocoapods/search?q=%5BXcodeproj%5D%20Unknown%20object%20version.&type=Issues&ut
SOLUTION:
To my particularly specific problem, I had permission issues with the RUBYGEMS that is installed by default on all MAC devices.
I was not able to rebase my project to its original state as I did not have "write privileges". I had to install homebrew and rbenv which allowed me to (after deleting my cocoapods out of the project entirely) rebase my project to its original state before whatever I had done to rebase the file target to something else.
After installing Homebrew and Rbenv I installed a newer version of RubyGem which gave me admin permissions on the new install. Then I reinstalled cocoapods to the project and VOILA. Problem solved.
I get error when try install pods with bot.
Could someone please explain what the problem is?
I checked this solution on Setting up Xcode 6 and Apple Server 4.0 for Continuous Integration with Cocoapods
Before integration script:
export LANG=en_US.UTF-8
cd ./CIT
pwd
pod install --verbose
Error:
/Library/Developer/XcodeServer/Integrations/Caches/27e5cbb07ffa7d7771a63d27e6002e1e/Source/CIT
Preparing
Updating local specs repositories
Updating spec repo `master`
$ /Applications/Xcode.app/Contents/Developer/usr/bin/git pull --ff-only
Updating dc43eae..957650b
Analyzing dependencies
Inspecting targets to integrate
Using `ARCHS` setting to build architectures of target `Pods`: (``)
Finding Podfile changes
- AFNetworking
Resolving dependencies of `Podfile`
[!] Unable to satisfy the following requirements:
- `AFNetworking` required by `Podfile`
- `AFNetworking (= 2.6.0)` required by `Podfile.lock`
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/resolver.rb:388:in `handle_resolver_error'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/resolver.rb:69:in `rescue in resolve'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/resolver.rb:56:in `resolve'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/installer/analyzer.rb:535:in `block in resolve_dependencies'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/user_interface.rb:59:in `section'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/installer/analyzer.rb:533:in `resolve_dependencies'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/installer/analyzer.rb:70:in `analyze'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/installer.rb:210:in `analyze'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/installer.rb:133:in `block in resolve_dependencies'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/user_interface.rb:59:in `section'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/installer.rb:132:in `resolve_dependencies'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/installer.rb:104:in `install!'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/command/project.rb:71:in `run_install_with_update'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/command/project.rb:101:in `run'
/Library/Ruby/Gems/2.0.0/gems/claide-0.9.1/lib/claide/command.rb:312:in `run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/lib/cocoapods/command.rb:48:in `run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.38.2/bin/pod:44:in `<top (required)>'
/usr/bin/pod:23:in `load'
/usr/bin/pod:23:in `<main>'
error: Your local changes to the following files would be overwritten by merge:
CocoaPods-version.yml
Specs/ASStarRatingView/0.1.0/ASStarRatingView.podspec.json
Specs/AppNexusOASSDK/1.0.0/AppNexusOASSDK.podspec.json
Specs/CrashlyticsFramework/2.1.6/CrashlyticsFramework.podspec.json
Specs/CrashlyticsFramework/2.1.7/CrashlyticsFramework.podspec.json
Specs/CrashlyticsFramework/2.1.9/CrashlyticsFramework.podspec.json
Specs/CrashlyticsFramework/2.2.0/CrashlyticsFramework.podspec.json
Specs/CrashlyticsFramework/2.2.1/CrashlyticsFramework.podspec.json
Specs/CrashlyticsFramework/2.2.10/CrashlyticsFramework.podspec.json
Specs/CrashlyticsFramework/2.2.2/CrashlyticsFramework.podspec.json
Specs/CrashlyticsFramework/2.2.3/CrashlyticsFramework.podspec.json
Specs/CrashlyticsFramework/2.2.4/CrashlyticsFramework.podspec.json
Specs/CrashlyticsFramework/2.2.5.1/CrashlyticsFramework.podspec.json
Specs/CrashlyticsFramework/2.2.5.2/CrashlyticsFramework.podspec.json
Specs/CrashlyticsFramework/2.2.5/CrashlyticsFramework.podspec.json
Specs/CrashlyticsFramework/2.2.9/CrashlyticsFramework.podspec.json
Specs/FlurrySDK/3.0.9/FlurrySDK.podspec.json
Specs/FlurrySDK/4.0.1/FlurrySDK.podspec.json
Specs/FlurrySDK/4.0.4/FlurrySDK.podspec.json
Specs/FlurrySDK/4.0.5/FlurrySDK.podspec.json
Specs/FlurrySDK/4.1.0/FlurrySDK.podspec.json
Specs/FlurrySDK/4.2.1/FlurrySDK.podspec.json
Specs/FlurrySDK/4.2.2/FlurrySDK.podspec.json
Specs/FlurrySDK/4.2.3/FlurrySDK.podspec.json
Specs/FlurrySDK/4.2.4/FlurrySDK.podspec.json
Specs/FlurrySDK/4.3.0/FlurrySDK.podspec.json
Specs/FlurrySDK/4.3.1/FlurrySDK.podspec.json
Specs/FlurrySDK/4.3.2/FlurrySDK.podspec.json
Specs/FlurrySDK/4.4.0/FlurrySDK.podspec.json
Specs/FlurrySDK/5.0.0/FlurrySDK.podspec.json
Specs/FlurrySDK/5.1.0/FlurrySDK.podspec.json
Specs/FlurrySDK/5.2.0/FlurrySDK.podspec.json
Specs/FlurrySDK/5.3.0/FlurrySDK.podspec.json
Specs/FlurrySDK/5.4.0/FlurrySDK.podspec.json
Specs/FlurrySDK/6.0.0/FlurrySDK.podspec.json
Specs/FlurrySDK/6.2.0/FlurrySDK.podspec.json
Specs/FlurrySDK/6.4.0/FlurrySDK.podspec.json
Specs/FlurrySDK/6.5.0/FlurrySDK.podspec.json
Specs/Google-Maps-iOS-SDK/1.9.2/Google-Maps-iOS-SDK.podspec.json
Specs/LibComponentLogging-pods/0.0.1/LibComponentLogging-pods.podspec.json
Specs/LibComponentLogging-pods/0.0.2/LibComponentLogging-pods.podspec.json
Specs/Moya/0.6.1/Moya.podspec.json
Specs/Moya/0.6/Moya.podspec.json
Specs/Moya/0.7.0/Moya.podspec.json
Specs/Moya/0.7.1/Moya.podspec.json
Specs/Moya/0.8.0/Moya.podspec.json
Specs/Moya/1.0.0/Moya.podspec.json
Specs/Moya/1.1.0/Moya.podspec.json
Specs/Moya/1.1.1/Moya.podspec.json
Specs/OpenCV/2.4.10/OpenCV.podspec.json
Specs/OpenCV/2.4.9/OpenCV.podspec.json
Specs/PromiseKit/1.5.3/PromiseKit.podspec.json
Specs/RxSwift/0.7.1/RxSwift.podspec.json
Specs/RxSwift/0.7/RxSwift.podspec.json
Specs/RxSwift/0.8/RxSwift.podspec.json
Specs/RxSwift/0.9/RxSwift.podspec.json
Specs/RxSwift/1.0/RxSwift.podspec.json
Specs/RxSwift/1.1/RxSwift.podspec.json
Specs/RxSwift/1.2.1/RxSwift.podspec.json
Specs/RxSwift/1.2/RxSwift.podspec.json
Specs/RxSwift/1.3/RxSwift.podspec.json
Specs/RxSwift/1.4/RxSwift.podspec.json
Specs/RxSwift/1.5/RxSwift.podspec.json
Specs/RxSwift/1.6/RxSwift.podspec.json
Specs/TSMessages/0.9.10/TSMessages.podspec.json
Specs/TSMessages/0.9.11/TSMessages.podspec.json
Specs/TSMessages/0.9.12/TSMessages.podspec.json
Specs/TSMessages/0.9.4/TSMessages.podspec.json
Specs/TSMessages/0.9.5/TSMessages.podspec.json
Specs/TSMessages/0.9.6/TSMessages.podspec.json
Specs/TSMessages/0.9.7/TSMessages.podspec.json
Specs/TSMessages/0.9.8/TSMessages.podspec.json
Specs/TSMessages/0.9.9/TSMessages.podspec.json
Specs/UIView+Wiggle/1.0.0/UIView+Wiggle.podspec.json
Specs/UIView+Wiggle/1.0.1/UIView+Wiggle.podspec.json
Specs/UIView+Wiggle/1.0.2/UIView+Wiggle.podspec.json
Specs/toxcore-ios/0.1.0/toxcore-ios.podspec.json
Specs/toxcore-ios/0.1.1/toxcore-ios.podspec.json
Specs/toxcore-ios/0.1.2/toxcore-ios.podspec.json
Specs/toxcore-ios/0.1.3/toxcore-ios.podspec.json
Specs/toxcore-ios/0.1.4/toxcore-ios.podspec.json
Specs/toxcore-ios
Aborting
[!] CocoaPods was not able to update the `master` repo. If this is an unexpected issue and persists you can inspect it running `pod repo update --verbose`
I needed to reset the Cocoapods repo that is utilized by user _xcsbuildd on my XcodeServer in order to get past the problem noted above. Here's how I did that:
1) On your OS X Server (running XcodeServer), select 'Users' from the Server Window, then right click on '_xcsbuildd' and select 'Advanced Options...'. Change the 'Login shell' from '/bin/false' to '/bin/bash'. (This will allow you to login as user '_xcsbuildd' from a terminal window.)
2) From a terminal window on OS X Server, login as any user. Then, to login as '_xcsbuildd', use sudo su - _xcsbuildd.
3) Remove the Cocoapods repo for user _xcsbuildd using rm -rf ~/.cocoapods.
4) Finally, integrate your BOT from your Xcode development client which will rebuild the Cocoapods repo as part of its before integration trigger step.
(My client environment is OS X 10.11 and Xcode 7.0.1, while my server environment is OS X 10.11, OS X Server 5.0.4, and Xcode 7.0.1. Cocoapods version is 0.38.2)
The following reference was helpful to me: http://honzadvorsky.com/articles/2015-08-17-17-30-xcode_server_tutorials_3_prebuild__postbuild_scripts/.
I am getting the error below following the tutorial in the book Learn Ruby on Rails.
I am able to launch my app manually by typing the URL into my browser but am wondering why Heroku open does not work.
Any idea what is happening here?
Heroku open error...
$ heroku open
Opening peaks-app... failed
! Heroku client internal error.
! Search for help at: https://help.heroku.com
! Or report a bug at: https://github.com/heroku/heroku/issues/new
Error: Unable to find a browser command. If this is unexpected, Please rerun with environment variable LAUNCHY_DEBUG=true or the '-d' commandline option and file a bug at
https://github.com/copiousfreetime/launchy/issues/new (Launchy::CommandNotFoundError)
Backtrace: /home/action/.heroku/client/vendor/gems/launchy-2.4.2/lib/launchy/applications/browser.rb:63:in `browser_cmdline'
/home/action/.heroku/client/vendor/gems/launchy-2.4.2/lib/launchy/applications/browser.rb:67:in `cmd_and_args'
/home/action/.heroku/client/vendor/gems/launchy-2.4.2/lib/launchy/applications/browser.rb:78:in `open'
/home/action/.heroku/client/vendor/gems/launchy-2.4.2/lib/launchy.rb:29:in `open'
/home/action/.heroku/client/lib/heroku/helpers.rb:328:in `block in launchy'
/home/action/.heroku/client/lib/heroku/helpers.rb:227:in `action'
/home/action/.heroku/client/lib/heroku/helpers.rb:326:in `launchy'
/home/action/.heroku/client/lib/heroku/command/apps.rb:342:in `open'
/home/action/.heroku/client/lib/heroku/command.rb:217:in `run'
/home/action/.heroku/client/lib/heroku/cli.rb:33:in `start'
/home/action/.parts/bin/heroku:24:in `<main>'
Command: heroku open
Version: heroku-toolbelt/3.12.1 (x86_64-linux) ruby/2.1.1
The short answer is that Heroku uses Launchy to launch my app and Launchy is looking for my browser. Since I am using Nitrous.io, I do not have a browser installed, so Launchy does not know what to do.
The author of Launchy explains that "...launching a browser from within the virtual box would do nothing if there was no browser installed." https://github.com/copiousfreetime/launchy/issues/78
Launching manually appears to be my only option at this point.
I installed vagrant 1.3.4 on my Windows 7 laptop then tried to type vagrant init from command line. It failed with below error. I tried other commands (even vagrant --help) but still receive a same error. I tried googling for a while to no avail. Is there anyone who can shed light on why this error happens? Any input is appreciated. Thanks
C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:268:in `[]': code converter not found (
UTF-16LE to Windows-1258) (Encoding::ConverterNotFoundError)
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:268:in `block in _all'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:267:in `each'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:267:in `_all'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:410:in `each'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:216:in `find_all'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:216:in `matching_specs'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:238:in `to_specs'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in `to_spec'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in `gem'
from C:/HashiCorp/Vagrant/bin//../embedded/../embedded/gems/bin/vagrant:22:in `<main>'
After searching for a while, this seems to be an issue with Ruby and I found the answer from this here:
Error installing Rubygems on ruby command prompt in Win7
I did the same, changing my locale from Vietnam to US and issue resolved.
You can add chcp 65001 > nul at the top of vagrant.bat after #ECHO OFF
I'm trying to migrate a blog from Tumblr to Octopress.
When I run in the octopress directory
ruby -rubygems -e 'require "jekyll/migrators/tumblr"; Jekyll::Tumblr.process("http://example.org", format="md")'
It starts running but then complains about what folder it's in
/usr/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/convertible.rb:27:in `read': No such file or directory - /usr/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/migrators/../_posts/tumblr/2012-08-28-how-to-add-your-picture-to-google-results.md (Errno::ENOENT)
from /usr/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/convertible.rb:27:in `read_yaml'
from /usr/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/post.rb:39:in `initialize'
from /usr/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/migrators/tumblr.rb:124:in `new'
from /usr/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/migrators/tumblr.rb:124:in `block in rewrite_urls_and_redirects'
from /usr/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/migrators/tumblr.rb:119:in `map'
from /usr/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/migrators/tumblr.rb:119:in `rewrite_urls_and_redirects'
from /usr/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/migrators/tumblr.rb:30:in `process'
from -e:1:in `<main>'
Here's a quick and dirty fix that worked for me (doesn't apply if you don't have root access, obviously), but it will get the job done.
Here's your error message for reference:
/usr/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/convertible.rb:27:in `read': \
No such file or directory - \
/usr/lib/ruby/gems/1.9.1/gems/jekyll0.11.2/lib/jekyll/migrators/../_posts/tumblr/2012-08-28-how-to-add-your-picture-to-google-results.md (Errno::ENOENT)
The full path in the exception is:
/usr/lib/ruby/gems/1.9.1/gems/jekyll0.11.2/lib/jekyll/migrators/../_posts/tumblr/2012-08-28-how-to-add-your-picture-to-google-results.md
Here's the solution:
1. cd to /usr/lib/ruby/gems/1.9.1/gems/jekyll0.11.2/lib/jekyll/migrators/
2. cd ..
3. ln -s %{DIRECTORY_WHERE__posts_LIVES}
4. Re-run your migration command
Just creating this symlink fixes the issue but it's an obvious and total hack.
Does the file /usr/lib/ruby/gems/1.9.1/gems/jekyll-0.11.2/lib/jekyll/_posts/tumblr/2012-08-28-how-to-add-your-picture-to-google-results.md exist? If not maybe you could just move your posts to that folder first, just as a simply workaround.