On Jan 4, 2010, at 1:09 PM, Paul Burba wrote: > On Mon, Jan 4, 2010 at 12:11 PM, Hyrum K. Wright > <hyrum_wri...@mail.utexas.edu> wrote: >> There have been several reports of problems in the 1.6.7 tarballs, so I'm >> feeling inclined to pull them and re-roll as 1.6.8 with the most recent >> fixes on the 1.6.x branch. I would not reroll until the ruby binding >> segfault has been fixed. >> >> Thoughts? > > AFAICT the ruby binding segfault is the only real problem with 1.6.7. > The python mergeinfo test failure mentioned by Stefan was due to > incorrect test expectations. Bhuvaneswaran's build problems sound > like issues with his setup. Is there anything else? > > Regardless, assuming the Ruby segfault is a regression, I'm all for > skipping 1.6.7 and rolling 1.6.8 once it is fixed...so, is anybody > looking at that?
Joe included his analysis of what's causing the failure, as well as a patch that fixes it here: http://svn.haxx.se/dev/archive-2009-12/0529.shtml Although it may fix the symptom, I'm not sure what the problem is, and haven't yet looked in depth. Julian took a look at it, but reported on IRC he couldn't see anything obvious. Perhaps more eyes would be useful. -Hyrum
