We've had multiple reports of this today. We've tracked it down to a bug on our side and should have a fix live in production soon. I'll keep you posted.
Thanks, Ryan On Aug 20, 2009, at 1:37 PM, Andrei Erdoss <[email protected]> wrote: > Hello, > > I tried to deploy my app to Heroku. The push went ok, but I'm > getting this error during 'heroku rake db:migrate' - RubyGem version > error: rubyforge(1.0.3 not >= 1.0.4) > > Ofcourse, I added this line to my .gems file - rubyforge --version > '>= 1.0.4'. After commiting this change, during the gems > installation Heroku is skipping that gem because it's already > installed. > > -----> Skipping rubyforge >= 1.0.4 - this gem is installed by > default on Heroku > > > So can someone please make some sense out of this. > > Thanks, > > -- > Andrei Erdoss > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
