Dane Springmeyer

I'm hitting this now trying to publish `node-eio`: ``` npm ERR! Error sending version data npm ERR! Error: os_process_error OS process timed out.: eio/0.0.3/-tag/latest npm ERR! at Request._callback (/usr/local/lib/node_modules/npm/lib/utils/npm-registry-client/request.js:180:12) npm...

@jhs - no, still hanging (latest attempt to publish has been running for ~5 minutes)

it ultimately died with: ``` npm http PUT https://registry.npmjs.org/eio npm http 409 https://registry.npmjs.org/eio npm http GET https://registry.npmjs.org/eio npm http 200 https://registry.npmjs.org/eio npm http PUT https://registry.npmjs.org/eio/0.1.0/-tag/latest npm ERR! Error sending version...

just tried again, no dice - still hanges. So I unpublished all of node-eio, and re-published, and that worked.

I forked and renamed to _zlib, and upgraded the wscript to work with node v6: https://github.com/springmeyer/node-zlib

/cc @springmeyer

Is this still relevant? https://github.com/mapbox/wagyu/pull/63 Upgrades to boost 1.63 - do you still think there is a boost bug present in 1.63? / cc @flippmoke

/cc @flippmoke @ericfischer

related (in terms of ability to catch errors): http://lists.osgeo.org/pipermail/gdal-dev/2011-February/027837.html

> it's a big undertaking that we haven't had much need for. I think @springmeyer and company are in the same boat. Yes, that's correct. We've not had a need...