I had this same problem last week - in the end, and on about the tenth push it finally managed to make it through which was a real pita.
Something needs to be there to ensure deployments aren't killed....whatever that might be. /Neil On 2 Nov 2009, at 16:46, markdevilliers wrote: > > It did work for me a couple of hours later. It had also failed several > times before I posted. > > I think the issue is consistency - random gems (not always redcloth) > were failing to install with the error message - "http:// > gemcutter.org/ does not appear to be a repository" - which in the > example above doesn't make sense as it was a repository moments > before. > > I'll probably accept that maybe gemcutter is a bit overloaded a > certain times and timing out delivering the initial 302 but maybe on > the heroku side there needs to be a "try a few times" on push as > failing at random stages is a bit annoying. > > Anyway I've just pushed again and all is good again, > > Thanks for looking into it for me - Mark > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
