Sublime Forum

Package Control: A full-featured package manager

#121

[size=120]as an idea:[/size]

sometimes interested in what’s new, but it is difficult to find

add to the panel item - [size=120]new plug-ins for the last month[/size]

0 Likes
#122

Hi wbond!

I have some plugins added via git.
For some reason “Package Control” when I use “Upgrade packages” command, it prompts me for the ssh key on each package! Problem is I have such 10 of these packages.

Is there any option to disable upgrade for git repositories? disabling GitUpgrader.

Thanks

0 Likes
#123

[quote=“rmaksim”][size=120]as an idea:[/size]

sometimes interested in what’s new, but it is difficult to find

add to the panel item - [size=120]new plug-ins for the last month[/size][/quote]

I should hopefully have this added to the website in the near future along with an RSS feed.

[quote=“tito”]Hi wbond!

I have some plugins added via git.
For some reason “Package Control” when I use “Upgrade packages” command, it prompts me for the ssh key on each package! Problem is I have such 10 of these packages.

Is there any option to disable upgrade for git repositories? disabling GitUpgrader.

Thanks[/quote]

You probably want to use the auto_upgrade_ignore setting wbond.net/sublime_packages/packa … l/settings

0 Likes
#124

Thanks wbond. Is not related to auto-upgrade, is about manually selecting “Upgrade packages” Looks like PC tries to check repositorires on github, *popuping * the ssh key error for each package on git.

0 Likes
#125

I haven’t been able to update or install anything. I get this error when trying to launch the quick panel.

File ".\Package Control.py", line 1706, in show_quick_panel TypeError: No registered converter was able to produce a C++ rvalue of type class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > from this Python object of type NoneType

EDIT

Ok I removed some custom repos from my user config file and it seems to work again now. It was after removing these two…

"https://github.com/ChrisKempson/TextMate-Tomorrow-Theme", "https://github.com/skt84/Themr"

0 Likes
#126

[quote=“firefusion”]I haven’t been able to update or install anything. I get this error when trying to launch the quick panel.

File ".\Package Control.py", line 1706, in show_quick_panel TypeError: No registered converter was able to produce a C++ rvalue of type class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > from this Python object of type NoneType

EDIT

Ok I removed some custom repos from my user config file and it seems to work again now. It was after removing these two…

"https://github.com/ChrisKempson/TextMate-Tomorrow-Theme", "https://github.com/skt84/Themr"[/quote]

Hmm, that is interesting. Both of those are not currently in the default channel. I wonder if the bug is related to that. I’ll do a little digging tonight.

0 Likes
#127

I just released version 1.5.0 which fixes a whole handful of bugs and adds SSL certificate verification to prevent man in the middle attacks against automatic updates. wbond.net/sublime_packages/packa … /changelog includes details.

0 Likes
#128

I’m behind a proxy and although I have the “http_proxy” and “https_proxy” settings both set to the same thing. Every time I try to list packages to install or packages to upgrade, i get one ore more of the following errors in the console:

Package Control: Error downloading channel. URL error _ssl.c:480: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol downloading https://sublime.wbond.net/repositories.json.

A month ago, this was working fine for me. Has anything changed to break this behavior on the plugin side, or is there a problem with my company’s proxy?

0 Likes
#129

[quote=“Grant”]I’m behind a proxy and although I have the “http_proxy” and “https_proxy” settings both set to the same thing. Every time I try to list packages to install or packages to upgrade, i get one ore more of the following errors in the console:

Package Control: Error downloading channel. URL error _ssl.c:480: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol downloading https://sublime.wbond.net/repositories.json.

A month ago, this was working fine for me. Has anything changed to break this behavior on the plugin side, or is there a problem with my company’s proxy?[/quote]

Package Control has switched to using SSL for the default channel for security purposes. Without a secure connection that checks the SSL certificate, it is possible for a man-in-the-middle attack where an attacker could inject arbitrary python code onto your machine via the automatic upgrade mechanism.

Unfortunately, it appears that some proxies have trouble with the SSL connection to my server. From reading online, the best info I can find talks about problems with different versions of OpenSSL talking to each other. I am in the process of migrating the site to a brand new server. Hopefully this will be complete in the next week or so.

0 Likes
#130

I am looking for a detailed explanation of version numbers in Package Control. It seems by default, Package Control generates a version number like this

"version": "2012.03.19.08.38.37"

I am looking into providing upgrade messages for certain versions, but I am uncertain how to override the current versioning scheme.

I would like to have it just be something predictable like:

"version": "1.7.0", but I can’t seem to figure out how to do this. Documentation isn’t very good on this, or I am not very good at determining this from the documentation. I see other packages doing this without anything special. Am I just missing something? Are the messages not connected to the version number in package-metadata.json?

0 Likes
#131

It’s probably not a critical thing, but when I upgrade packages I get the following output in my console:

[quote]Package Control: Error downloading repository. HTTP error 404 downloading sublime.wbond.net/debug/packages.json.
Package Control: Error downloading repository. HTTP error 404 downloading sublime.wbond.net/debug/packages.json.[/quote]

I had a quick look for any references to this repository in my config but couldn’t find anything.

0 Likes
#132

[quote=“peppy”]It’s probably not a critical thing, but when I upgrade packages I get the following output in my console:

[quote]Package Control: Error downloading repository. HTTP error 404 downloading sublime.wbond.net/debug/packages.json.
Package Control: Error downloading repository. HTTP error 404 downloading sublime.wbond.net/debug/packages.json.[/quote]

I had a quick look for any references to this repository in my config but couldn’t find anything.[/quote]

That’s a really old package channel I shared with a few users while testing out fixes for my SFTP package. You need to go to Preferences > Package Settings > Package Control > Settings - User and delete that repository from the list.

0 Likes
#133

Why did my spotlight search not find that entry :frowning:. Thanks! feels silly

(sftp has been working really nicely lately, by the way! ftp support has come in handy with some archaic stuff i’ve been working on recently, too.)

0 Likes
#134

[quote=“Grant”]I’m behind a proxy and although I have the “http_proxy” and “https_proxy” settings both set to the same thing. Every time I try to list packages to install or packages to upgrade, i get one ore more of the following errors in the console:

Package Control: Error downloading channel. URL error _ssl.c:480: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol downloading https://sublime.wbond.net/repositories.json.

A month ago, this was working fine for me. Has anything changed to break this behavior on the plugin side, or is there a problem with my company’s proxy?[/quote]

I just finished moving sublime.wbond.net to a new server, which should hopefully solve this issue. Please let me know what you find.

0 Likes
#135

[quote=“wbond”]

[quote=“Grant”]I’m behind a proxy and although I have the “http_proxy” and “https_proxy” settings both set to the same thing. Every time I try to list packages to install or packages to upgrade, i get one ore more of the following errors in the console:

Package Control: Error downloading channel. URL error _ssl.c:480: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol downloading https://sublime.wbond.net/repositories.json.

A month ago, this was working fine for me. Has anything changed to break this behavior on the plugin side, or is there a problem with my company’s proxy?[/quote]

I just finished moving sublime.wbond.net to a new server, which should hopefully solve this issue. Please let me know what you find.[/quote]

Hello. I am new to Sublime Text and just tried Package Control. Unfortunately, I keep getting the exact same error message when using the HTTPS address. Without SSL it works fine. A connection from other tools like an ICQ server via SSL (using Miranda IM) also works, so I don’t think it is a proxy problem in general. Would be nice if you could try to find the error (no hurry). :smile:

0 Likes
#136

[quote=“qwertfisch”]

I just finished moving sublime.wbond.net to a new server, which should hopefully solve this issue. Please let me know what you find.
Hello. I am new to Sublime Text and just tried Package Control. Unfortunately, I keep getting the exact same error message when using the HTTPS address. Without SSL it works fine. A connection from other tools like an ICQ server via SSL (using Miranda IM) also works, so I don’t think it is a proxy problem in general. Would be nice if you could try to find the error (no hurry). :smile:[/quote]

What platform are you running? If you are on Linux, I’ve heard reports that some old version of OpenSSL don’t work well with newer versions. Perhaps you need to upgrade openssl and curl/wget.

On the server I am running OpenSSL 1.0.0 and Apache 2.4, so that should not be the culprit any longer. I’m basically out of ideas on how to help people with these networking issues.

0 Likes
#137

[quote=“wbond”]

Hello. I am new to Sublime Text and just tried Package Control. Unfortunately, I keep getting the exact same error message when using the HTTPS address. Without SSL it works fine. A connection from other tools like an ICQ server via SSL (using Miranda IM) also works, so I don’t think it is a proxy problem in general. Would be nice if you could try to find the error (no hurry). :smile:

What platform are you running? If you are on Linux, I’ve heard reports that some old version of OpenSSL don’t work well with newer versions. Perhaps you need to upgrade openssl and curl/wget.[/quote]

I am running Windows7 x64 (SP1) at work. I cannot think of any possibility why it won’t work, since everything else with SSL is no problem.

Just a question, is it possible to use http links in the .json file, when downloading it from sublime.wbond.net/repositories.json? I don’t see much sense to offer a non-SSL link where its content points again to https, which I cannot download. If I could use HTTPS I would use the HTTPS version of the link …

0 Likes
#138

[quote=“wbond”]

[quote=“Grant”]I’m behind a proxy and although I have the “http_proxy” and “https_proxy” settings both set to the same thing. Every time I try to list packages to install or packages to upgrade, i get one ore more of the following errors in the console:

Package Control: Error downloading channel. URL error _ssl.c:480: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol downloading https://sublime.wbond.net/repositories.json.

A month ago, this was working fine for me. Has anything changed to break this behavior on the plugin side, or is there a problem with my company’s proxy?[/quote]

I just finished moving sublime.wbond.net to a new server, which should hopefully solve this issue. Please let me know what you find.[/quote]

I noticed that my office has started preferring the “Automatically detect settings” in the Control Panel -> Interntet Properties -> LAN Settings for Windows (I’m using Windows 7 64bit). I found an article over at stackoverflow on how to do this. Any way it might help in case some of us?

(NOTE: I just tried looking at the ‘wpad.dat’ file that was on our network and tried an alternate proxy in the list. Still got the same error, so I’m guessing the problem has something to do with SSL redirects through proxies. I know browsers like firefox and chrome detect this redirect and can make the user aware of it when it happens. The problem likely isn’t with wbond’s server, but more in how the redirects are handled in either the SSL library or in the Package Control code)

0 Likes
#139

Hi guys,
I’m having the same issues behind with an https proxy.
I tried to solve the problem by myself, but I’m not a python programmer :smiley:
However, I’m pretty sure that the problem is a know one and this python issue can help: http://bugs.python.org/issue1424152
The problem seems to be related to urllib2.
Hope this can help

0 Likes
#140

I have the same exact issue, on Windows 7 64bit. On Mac os is fine.

Regards

0 Likes