Unable to install latest showoff gem at heroku #109

Open
mikegrassotti opened this Issue Aug 10, 2011 · 2 comments

Comments

Projects
None yet
3 participants

I am trying to deploy a simple showoff presentation to heroku. Everything looks good when I run locally, but can't figure out how to use the latest version (0.5.1) of the showoff gem on heroku. At first, I just referenced gem 'showoff' in my Gemfile. That deployed ok, but I ended up with an old version (0.4.2) instead of the new one. Unfortunately my presentation looks really bad with that version, so wanted to use the latest.

Tried forcing version to the latest, but then it was not found. So I updated Gemfile to reference the github repo directly. On my machine (ruby 1.9.3) "bundle install" downloads the repo and builds the gem, but Heroku fails with this error:

   There was a LoadError while evaluating showoff.gemspec:
     no such file to load -- sinatra/base from
     /disk1/tmp/build_fhfxoh2is5so/.bundle/gems/ruby/1.9.1/bundler/gems/showoff-76c8e3042d1b/showoff.gemspec:1:in `<main>'

   Does it try to require a relative path? That doesn't work in Ruby 1.9.
   FAILED: http://devcenter.heroku.com/articles/bundler

! Heroku push rejected, failed to install gems via Bundler

My Gemfile looks like this:

source :rubygems
gem 'sinatra'
gem 'bluecloth'
gem 'nokogiri'
gem 'json'
gem 'parslet'
gem 'showoff', :git => "git://github.com/schacon/showoff.git"
gem 'gli'

It's been a while since I used heroku, so maybe I'm missing something simple. Any advice?

Owner

schacon commented Sep 11, 2011

try the newest one - 0.6.0

A little OT, but I've run into the same issue with a different gem - I can't get heroku to install from the github repo the way my local machine does.

I get the same error reported above when I deploy with a Gemfile sourcing a repo on github, and have started to wonder if I'm overlooking something, or if the sourcing syntax has changed.

EDIT: I'm going to suppose that the gem in question is the problem, and go bark up that tree.

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