Vince, After looking a 2nd time at my history, it seems like I might have given up on the migration to 1.9.2 and just gone with a recreation:
heroku create --stack bamboo-mri-1.9.2 Scott On Thu, Dec 30, 2010 at 9:57 AM, Vincent Coste <[email protected]>wrote: > Okay, I don't have a .gems but un Gemfile. And i have pg defined into it. > > > Her is the content of my Gemfile; > > source 'http://rubygems.org' >> >> >>> gem 'rails', '3.0.1' >> >> >>> gem 'nokogiri' >> >> gem 'jquery-rails' >> >> gem 'haml' >> >> gem 'devise' >> >> gem 'omniauth' >> >> gem "friendly_id", "~> 3.1" >> >> >>> gem 'sqlite3-ruby', :require => 'sqlite3' >> >> >>> group :production do >> >> gem "pg" >> >> end >> >> >>> group :development, :test do >> >> gem 'machinist', '>= 2.0.0.beta1' >> >> gem 'fakeweb' >> >> gem 'mocha' >> >> gem 'compass' >> >> end >> >> >> > > The weird thing is that when I git push, the logs tell me that the stack > changes from 1.8.7 to 1.9.2, but actually not. > > Weird! > > > > On Thu, Dec 30, 2010 at 6:15 PM, Scott LaBounty <[email protected]>wrote: > >> Vince, >> >> OK, now I'm with you. I think what finally did it was to put "pg" in my >> .gems file rather than "pg-ruby". If that doesn't work, let me know and I'll >> look a bit more. >> >> Scott >> >> >> On Thu, Dec 30, 2010 at 7:18 AM, Vincent Coste >> <[email protected]>wrote: >> >>> Hi Scott, thanks for the faste answer. >>> >>> Actually, my question was more about what kind of code push did you do in >>> order to migrate your stack? I have almost the same problem you had: >>> >>> git push heroku master >>> >>> Counting objects: 87, done. >>> >>> Delta compression using up to 2 threads. >>> >>> Compressing objects: 100% (48/48), done. >>> >>> Writing objects: 100% (50/50), 7.23 KiB, done. >>> >>> Total 50 (delta 31), reused 0 (delta 0) >>> >>> >>>> -----> Heroku receiving push >>> >>> -----> Migrating from bamboo-ree-1.8.7 to bamboo-mri-1.9.2 >>> >>> >>> [......] >>> >>> >>> Your bundle is complete! It was installed into ./.bundle/gems >>> >>> -----> Installing Exceptional plugin from git:// >>> github.com/contrast/exceptional.git... done. >>> >>> Compiled slug size is 6.7MB >>> >>> -----> Launching... done >>> >>> deployed to Heroku >>> >>> >>> -----> Migration complete, your app is now running on bamboo-mri-1.9.2 >>> >>> >>> >>> >>> >>> >>> And on an heroku stack: >>> >>> heroku stack >>> >>> aspen-mri-1.8.6 >>> >>> * bamboo-ree-1.8.7 >>> >>> bamboo-mri-1.9.1 (beta) >>> >>> bamboo-mri-1.9.2 (beta) (prepared, will migrate on next git push) >>> >>> >>> >>> >>> If i can't do it soon, i think i'm gonna recreate an app directly with >>> the right stack. >>> >>> Regards, >>> >>> >>> >>> On Wed, Dec 29, 2010 at 8:06 PM, Scott LaBounty <[email protected]>wrote: >>> >>>> Vince, >>>> >>>> Here's a post I did on Heroku and Sequel ... >>>> >>>> http://steamcode.blogspot.com/2010/09/sequel-and-heroku.html >>>> >>>> To push your database do: >>>> >>>> heroku db:push sqlite://mydatabase.sqlite >>>> heroku restart >>>> >>>> Is this what you're looking for? If not, let me know and I'll see what >>>> else I've got. Locally, I just use sqlite and then pretty much everything >>>> works on Heroku with Postgres. >>>> >>>> Scott >>>> >>>> On Wed, Dec 29, 2010 at 5:26 AM, Vincent Coste <[email protected] >>>> > wrote: >>>> >>>>> Just to know, what did you push in order for heroku to migrate your >>>>> stack? >>>>> >>>>> On Dec 13, 11:20 pm, Scott LaBounty <[email protected]> wrote: >>>>> > Thanks! That cleared up one problem anyway. It looks like I may have >>>>> other >>>>> > issues, but I'll try to work them out. >>>>> > >>>>> > Scott >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > On Mon, Dec 13, 2010 at 2:00 PM, Robert Eanes <[email protected]> >>>>> wrote: >>>>> > > You want the pg gem, not the ruby-pg gem, which looks like it >>>>> hasn't been >>>>> > > updated since 2008. I've used it locally and on heroku with 1.9.2 >>>>> > > successfully. >>>>> > >>>>> > > On Dec 13, 2010, at 3:49 PM, Scott LaBounty wrote: >>>>> > >>>>> > > > OK, continuing on here. I just use sqlite locally for development >>>>> and >>>>> > > don't have postgres installed. I get the same error when I try to >>>>> install it >>>>> > > on my machine. Is the ruby-pg gem incompatible with ruby 1.9.2? If >>>>> so, then >>>>> > > how on earth does the 1.9.2 stack work for anything on Heroku? >>>>> > >>>>> > > > Scott >>>>> > >>>>> > > > On Mon, Dec 13, 2010 at 12:38 PM, Scott LaBounty < >>>>> [email protected]> >>>>> > > wrote: >>>>> > > > One more thought ... would it help to delete the app and then >>>>> regenerate >>>>> > > it with ruby 1.9.2 to start with? For the record, I'm using Ramaze >>>>> and >>>>> > > Sequel here, not Rails. >>>>> > >>>>> > > > Scott >>>>> > >>>>> > > > On Mon, Dec 13, 2010 at 10:49 AM, Scott LaBounty < >>>>> [email protected]> >>>>> > > wrote: >>>>> > > > OK, when I changed something and did a new push, I get ... >>>>> > >>>>> > > > << >>>>> > > > -----> Installing gem ruby-pg fromhttp://rubygems.org >>>>> > > > Building native extensions. This could take a while... >>>>> > > > ERROR: Error installing ruby-pg: >>>>> > > > ERROR: Failed to build gem native extension. >>>>> > >>>>> > > > /usr/ruby1.9.2/bin/ruby extconf.rb >>>>> > > > *** extconf.rb failed *** >>>>> > > > Could not create Makefile due to some reason, probably >>>>> lack of >>>>> > > > necessary libraries and/or headers. Check the mkmf.log >>>>> file for >>>>> > > more >>>>> > > > details. You may need configuration options. >>>>> > >>>>> > > > Provided configuration options: >>>>> > > > --with-opt-dir >>>>> > > > --without-opt-dir >>>>> > > > --with-opt-include >>>>> > > > --without-opt-include=${opt-dir}/include >>>>> > > > --with-opt-lib >>>>> > > > --without-opt-lib=${opt-dir}/lib >>>>> > > > --with-make-prog >>>>> > > > --without-make-prog >>>>> > > > --srcdir=. >>>>> > > > --curdir >>>>> > > > --ruby=/usr/ruby1.9.2/bin/ruby >>>>> > > > extconf.rb:4:in `<main>': uninitialized constant >>>>> Object::PLATFORM >>>>> > > (NameError) >>>>> > >>>>> > > > Gem files will remain installed in >>>>> > > /code/repos/377655/gems_build/gems/ruby-pg-0.7.9.2008.01.28 for >>>>> inspection. >>>>> > > > Results logged to >>>>> > > >>>>> /code/repos/377655/gems_build/gems/ruby-pg-0.7.9.2008.01.28/ext/gem_make.ou >>>>> t >>>>> > > > ! Heroku push rejected, failed to install gem >>>>> > >>>>> > > > It looks like the ruby-pg gem won't build with 1.9.2? >>>>> > >>>>> > > > Scott >>>>> > >>>>> > > > On Mon, Dec 13, 2010 at 9:59 AM, Scott LaBounty < >>>>> [email protected]> >>>>> > > wrote: >>>>> > > > All, >>>>> > >>>>> > > > I was getting the following error: >>>>> > >>>>> > > > << >>>>> > >>>>> > > >>>>> /disk1/home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/ >>>>> mnt/model/init.rb:10: >>>>> > > undefined method `require_relative' for main:Object (NoMethodError) >>>>> > > > 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 >>>>> > > >>>>> /disk1/home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/ >>>>> mnt/app.rb:13 >>>>> > > > 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:18 >>>>> > > > from /home/heroku_rack/heroku.ru:23 >>>>> > > > from >>>>> > > >>>>> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g >>>>> ems/gems/rack-1.2.1/lib/rack/builder.rb:46:in >>>>> > > `instance_eval' >>>>> > > > from >>>>> > > >>>>> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g >>>>> ems/gems/rack-1.2.1/lib/rack/builder.rb:46:in >>>>> > > `initialize' >>>>> > > > from >>>>> > > >>>>> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g >>>>> ems/gems/rack-1.2.1/lib/rack/builder.rb:63:in >>>>> > > `new' >>>>> > > > from >>>>> > > >>>>> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g >>>>> ems/gems/rack-1.2.1/lib/rack/builder.rb:63:in >>>>> > > `map' >>>>> > > > from /home/heroku_rack/heroku.ru:18 >>>>> > > > from >>>>> > > >>>>> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g >>>>> ems/gems/rack-1.2.1/lib/rack/builder.rb:46:in >>>>> > > `instance_eval' >>>>> > > > from >>>>> > > >>>>> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g >>>>> ems/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/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g >>>>> ems/gems/rack-1.2.1/lib/rack/builder.rb:46:in >>>>> > > `instance_eval' >>>>> > > > from >>>>> > > >>>>> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g >>>>> ems/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 >>>>> > >>>>> > > > since "require_relative" is a 1.9.2 feature of ruby, I did a: >>>>> > >>>>> > > > heroku stack:migrate bamboo-mri-1.9.2 >>>>> > > > git push heroku master >>>>> > >>>>> > > > and I'm getting the same error. >>>>> > >>>>> > > > When I do a: >>>>> > >>>>> > > > heroku stack >>>>> > >>>>> > > > I see: >>>>> > >>>>> > > > aspen-mri-1.8.6 >>>>> > > > * bamboo-ree-1.8.7 >>>>> > > > bamboo-mri-1.9.1 (beta) >>>>> > > > bamboo-mri-1.9.2 (beta) (prepared, will migrate on next git >>>>> push) >>>>> > >>>>> > > > so I tried doing: >>>>> > >>>>> > > > touch README >>>>> > > > git push heroku master >>>>> > >>>>> > > > and the stack is still the same. What else do I need to do to >>>>> change the >>>>> > > stack? >>>>> > >>>>> > > > -- >>>>> > > > Scott >>>>> > > >http://steamcode.blogspot.com/ >>>>> > >>>>> > > > -- >>>>> > > > Scott >>>>> > > >http://steamcode.blogspot.com/ >>>>> > >>>>> > > > -- >>>>> > > > Scott >>>>> > > >http://steamcode.blogspot.com/ >>>>> > >>>>> > > > -- >>>>> > > > Scott >>>>> > > >http://steamcode.blogspot.com/ >>>>> > >>>>> > > > -- >>>>> > > > 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]<heroku%[email protected]> >>>>> <heroku%[email protected]<heroku%[email protected]> >>>>> > >>>>> > > . >>>>> > > > For more options, visit this group at >>>>> > >http://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]<heroku%[email protected]> >>>>> <heroku%[email protected]<heroku%[email protected]> >>>>> > >>>>> > > . >>>>> > > For more options, visit this group at >>>>> > >http://groups.google.com/group/heroku?hl=en. >>>>> > >>>>> > -- >>>>> > Scotthttp://steamcode.blogspot.com/ >>>> >>>> >>>> >>>> >>>> -- >>>> Scott >>>> http://steamcode.blogspot.com/ >>>> >>> >>> >>> >>> -- >>> Vincent COSTE >>> >> >> >> >> -- >> Scott >> http://steamcode.blogspot.com/ >> > > > > -- > Vincent COSTE > -- Scott http://steamcode.blogspot.com/ -- 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.
