I'm still having some trouble trying to use this. Near as I can tell,
this has to do with a difference between x86, and x64 based binaries,
but it only shows up when using the BUNDLE_WITHOUT var. The relevant
portion of my gemfile appears to be:
gem 'yajl-ruby', :require => 'yajl/json_gem' (which is included in
prod)
/home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-a7ee-3a6501df7384/
mnt/.bundle/gems/ruby/1.8/gems/yajl-ruby-0.7.8/lib/yajl_ext.so: /home/
slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-a7ee-3a6501df7384/
mnt/.bundle/gems/ruby/1.8/gems/yajl-ruby-0.7.8/lib/yajl_ext.so: wrong
ELF class: ELFCLASS64 - /home/slugs/
248304_edf2a45_2797-6d57a2ed-91b3-4d81-a7ee-3a6501df7384/mnt/.bundle/
gems/ruby/1.8/gems/yajl-ruby-0.7.8/lib/yajl_ext.so (LoadError)
from /home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/.bundle/gems/ruby/1.8/gems/yajl-ruby-0.7.8/lib/
yajl.rb:2
from /home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/.bundle/gems/ruby/1.8/gems/yajl-ruby-0.7.8/lib/
yajl/json_gem.rb:2:in `require'
from /home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/.bundle/gems/ruby/1.8/gems/yajl-ruby-0.7.8/lib/
yajl/json_gem.rb:2
from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/
runtime.rb:64:in `require'
from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/
runtime.rb:64:in `require'
from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/
runtime.rb:62:in `each'
from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/
runtime.rb:62:in `require'
from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/
runtime.rb:51:in `each'
from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/
runtime.rb:51:in `require'
from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/
bundler.rb:112:in `require'
from /mnt/home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/config/application.rb:15
from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
31:in `gem_original_require'
from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
31:in `require'
from /mnt/home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/config/environment.rb:2
from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
31:in `gem_original_require'
from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
31:in `require'
from config.ru:3
from /home/heroku_rack/heroku.ru:23
from /home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/.bundle/gems/ruby/1.8/gems/rack-1.2.1/lib/rack/
builder.rb:46:in `instance_eval'
from /home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/.bundle/gems/ruby/1.8/gems/rack-1.2.1/lib/rack/
builder.rb:46:in `initialize'
from /home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/.bundle/gems/ruby/1.8/gems/rack-1.2.1/lib/rack/
builder.rb:63:in `new'
from /home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/.bundle/gems/ruby/1.8/gems/rack-1.2.1/lib/rack/
builder.rb:63:in `map'
from /home/heroku_rack/heroku.ru:18
from /home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/.bundle/gems/ruby/1.8/gems/rack-1.2.1/lib/rack/
builder.rb:46:in `instance_eval'
from /home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/.bundle/gems/ruby/1.8/gems/rack-1.2.1/lib/rack/
builder.rb:46:in `initialize'
from /home/heroku_rack/heroku.ru:11:in `new'
from /home/heroku_rack/heroku.ru:11
from /home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/.bundle/gems/ruby/1.8/gems/rack-1.2.1/lib/rack/
builder.rb:46:in `instance_eval'
from /home/slugs/248304_edf2a45_2797-6d57a2ed-91b3-4d81-
a7ee-3a6501df7384/mnt/.bundle/gems/ruby/1.8/gems/rack-1.2.1/lib/rack/
builder.rb:46:in `initialize'
from /home/heroku_rack/heroku.ru:1:in `new'
from /home/heroku_rack/heroku.ru:1
Is there something obvious I'm missing here?
On Nov 8, 3:53 pm, Chris Hanks <[email protected]> wrote:
> It works! Thanks, Oren.
>
> On Nov 8, 12:05 pm, Oren Teich <[email protected]> wrote:
>
>
>
>
>
>
>
> > Bundlr 1.0.3 changed the syntax for without. We are deploying a
> > hotfix tomorrow. In the meantime, seperate the groups you don't want
> > deployed with a : instead of a space. e.g. heroku config:add
> > BUNDLER_WITHUOUT=development:test
>
> > Oren
>
> > On Mon, Nov 8, 2010 at 12:03 PM, Chris Hanks
>
> > <[email protected]> wrote:
> > > Yes, this started happening for me on Friday (worked fine up until
> > > then). and it looks like it's still going on. When I push I see "Using
> > > --without development test", but it tries to install all the
> > > development/test gems anyway (which it can't, for me, because Heroku
> > > can't handle ruby-debug19).
>
> > > I haven't had a burning need to deploy recently, so I've been waiting
> > > for Heroku to sort it out, but it looks like they haven't, yet.
>
> > > Anyway, it's definitely a bug, so why not open a support ticket about
> > > it? And maybe let us know how it works out?
>
> > > On Nov 6, 3:06 pm, Volkan Unsal <[email protected]> wrote:
> > >> I wanted Heroku's bundler to ignore some gems I have installed. It
> > >> doesn't manage to do that, and as a result I am getting lots of
> > >> errors.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Heroku" group.
> > > To post to this group, send email to [email protected].
> > > To unsubscribe from this group, send email to
> > > [email protected].
> > > For more options, visit this group
> > > athttp://groups.google.com/group/heroku?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
