I'm about to release the first new version of Package Control since early March. Yikes – that took way too long!

Please spend some time today if you can using the testing version. I am hoping to push out the new version tomorrow, Nov 20th, 2012.

If you can, please test:

Upgrading to the new version of Package Control

Installing packages

Removing packages

Upgrading a single package

Upgrading all packages

The link above covers some of the big additions/fixes. Also there have been fixes for handling upgrading in-use DLL files on Windows, not disabling packages when running upgrade all, handling non-ascii characters in the file path to the SSL CA certs bundle file, plus a whole bunch of other small things.

Nope, still getting "Package Control: Error downloading channel. URL error [Errno 10061] No connection could be made because the target machine actively refused it downloading https://sublime.wbond.net/repositories.json. This is even with http_proxy, proxy_username and proxy_password all configured manually.

I've never seen Package Control work at all on this box, though, so this isn't evidence of a regression.

MikeC wrote:Nope, still getting "Package Control: Error downloading channel. URL error [Errno 10061] No connection could be made because the target machine actively refused it downloading https://sublime.wbond.net/repositories.json. This is even with http_proxy, proxy_username and proxy_password all configured manually.

I've never seen Package Control work at all on this box, though, so this isn't evidence of a regression.

It sounds like you have a firewall or virus scanner blocking connection attempts. Every similar report I've heard has been caused by a program in one of those two categories.

Perhaps double-check that Mike. Modern firewalls are clever; they can inspect on more than just the source/target IP or DNS. For example, your browser will connect with a browser user agent (UA) string, whereas Package Control probably uses a custom UA string. A tight firewall may only let packets through with a known browser UA string, and could block anything that isn't a legitimate browser on port 80 for example.

If you can temporarily disable your firewall altogether for a moment and try that'll seal it