That sounds awfully plausible. Deleting/recreating the heroku app doesn't help, I'd already tried that at least a dozen times before I resorted to posting. But still, the idea of a bundle cache sounds quite likely. Unfortunately I so far haven't been able to find where that would exist. I've seen a few scant references to removing things from .bundle but I find no such directory. I tried pulling down a fresh clone from my archive repo and that didn't behave any differently. I guess the next step on that path is to try cloning to a fresh dev box and deploying from there. Or maybe nuking the ruby installation?
I'm also trying to pursue the cedar option but that seems to be a difficult road from windows. Getting thin to work is elusive so far (tried devkit, then tried preload of alternate version of eventmachine--still no luck) It looked like maybe thin was not actually *required* so I tried to go without. Was able to push to cedar then--but unlike bamboo cedar doesn't seem to list all the gems it's finding, so I can't tell if I got anywhere there. Db push is failing for some reason despite the fact that I dropped pg in a production block. Anyway, thank you for responding and giving me ideas on what to try next! I've put off this post hoping I'd be able to say something about "and what eventually worked was..." but I guess that's not happening today. Erich On Jun 7, 6:09 pm, David Dollar <da...@heroku.com> wrote: > This happens because rack 1.3.0 still exists in your app's bundler cache and > the stacks prior to cedar do not "bundle exec" when running your app. You > could work around this by deleting and recreating the app. You could also > give the cedar stack a try which does not have this issue. > > Cheers, > David > > > > > > > > On Tuesday, June 7, 2011 at 6:02 PM, Erich wrote: > > My app was working fine on the 1.9.2 branch, and it still runs fine > > locally. But now when I try to deploy to Heroku it crashes with this > > error in the log. > > > You have already activated rack 1.3.0, but your Gemfile requires rack > > 1.2.3. Consider using bundle exec. (Gem::LoadError) > > > I briefly had rails 3.1 installed but it's not on my system anymore. > > gem list and bundle list show no sign of rack 1.3.0. > > > But sure enough I do see this in response to an initial push: > > > remote: -----> Installing gem rack fromhttp://rubygems.org > > remote: Successfully installed rack-1.3.0 > > remote: 1 gem installed > > > As well as a lot of other things that aren't in my gemfile. > > > I thought maybe it was grabbing everything from my local gem list, but > > deleting them out doesn't get rid of them. > > > So where besides gemfile, gemfile.lock (ignored because I'm on > > windows, but I've still been checking it) and local gems would a push > > to heroku be finding gems to install? I know it's on my end, and > > something about the particular project, because a similar project on > > the same dev box is still able to deploy successfully. > > > Thanks in advance for any leads. > > > ec > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to heroku@googlegroups.com > > (mailto:heroku@googlegroups.com). > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com > > (mailto:heroku+unsubscr...@googlegroups.com). > > 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 heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
