Hello, I had that issue on Jessie and I went with packaging 0.4.3.
I would like to first thanks Gerald Turner for the investigation. He mentioned the NodeJS API has changed and also pointed out to an upstream change. The API change is fixed by: https://github.com/request/tunnel-agent/commit/7abb63b49ab0b30c35f224f2966d34c163b0505c agent.addRequest parameters have changed Gerald pointed: https://github.com/request/tunnel-agent/commit/3d979c3f26a6562f3744c4ca80c8b0716ec4a69f Fix various bugs with connection pool handling Both changes are included in 0.4.3 which also add: https://github.com/request/tunnel-agent/commit/a2c2c2acddd86dd6a894cf4ae53e696e796298c9 set the defaultPort to 443 for https agents I remember that one has been hitting me when I tried to setup a https proxy. The other changes with 0.3.1 are related to package.json or .jshintrc so hardly have any impact. So seems the easiest way is to just upgrade to 0.4.3 and I have confirmed it fix the issue. If one wants to upgrade further: * 0.5.x brings a new dependency "safe-buffer" which would need to be packaged I have forked collab-maint/node-tunnel-agent on Wikimedia Gerrit repo and did the patches there: https://gerrit.wikimedia.org/r/#/q/project:operations/debs/node-tunnel-agent+bug:183569 You can also find them on the Github mirror: https://github.com/wikimedia/operations-debs-node-tunnel-agent For reference, Wikimedia bug is: https://phabricator.wikimedia.org/T183569 -- Antoine "hashar" Musso -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
