Jon, According to gemcutter - http://gemcutter.org/gems/merb/versions/1.1.0.pre , the 1.1.0.pre release was made on November 17, so I suppose the latest from github on that date would be a fair guess - http://github.com/merb/merb/commits/master .
That said. I installed the HEAD version from github just yesterday, and haven't yet noticed the kind of problems you describe, although I'm on ruby 1.8.7 p72, so the problems you're seeing may be specific to 1.9. Mark. Jon Hancock wrote: > I updated merb with the latest from github, installs as "1.1.0.pre". > Now its busted. I'm using system installed gems and still have the > old gems which I installed a few months ago which are labelled > "1.1". I would very much like to know the git commit id for the old > 1.1 install so I can install a working merb on a production machine. > Any ideas? Also, any info as to when we can expect github's merb HEAD > to be in better working order? > thanks, Jon -- You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en.
