Sublime Forum

Package Control: A full-featured package manager

#111

[quote=“natebeaty”]I’ve been having a similar issue, using OS X Lion 10.7.1 and the latest dev version of ST2. This error pops up on start:

When I do Package Control: Discover, the error pops up again, and if I hit enter on any of the packages, it freezes ST2.[/quote]

It looks like you have an improper repository URL to your installation, although I could be wrong. I don’t believe Package Control ever uses URLs with .git at the end, which is why I think you may have added one. Please go to Preferences > Package Settings > Package Control > Settings - User. Delete any reference to SublimeLinter from your repositories setting. SublimeLinter is part of the default channel so you shouldn’t need to add . If it was there, after you delete it you should not longer get a 404 (not found) error. You should now be able to install SublimeLinter.

If this is not the case, please open a ticket on GitHub at github.com/wbond/sublime_package_control/issues. Unfortunately this forum isn’t a very good place for bug reports since there is no notification mechanism.

0 Likes
#112

Exactly how I fixed it (took me a second to figure out how to find that settings file). I guess I just posted this in case someone else had a similar issue.

Turns out this is user error, I thought I was supposed to copy/paste the repository URL, not the Git page URL (the same, but minus “.git” at the end). Maybe you should just strip /.git$/ when a user does a manual Add Repository?

Anyway, was an easy fix. Thanks for the great package manager, such a fantastic addition to ST2.

0 Likes
#113

If I recall correctly, it is GitHub that’s triggering these. Win 7

It’s infrequent enough that it’s not a huge issue, but when it happens it fires a bunch of them at the same time. Is there any way to simply make this silent and log it in an error log somewhere instead of throwing a bunch of alerts? I mean, how often do I really need to check GitHub now that I already have the packages? :smile:

Love the plugin though, blows every other IDE’s package management out of the water. Thanks for the hard work! :smile:

0 Likes
#114

[quote=“aple”]

If I recall correctly, it is GitHub that’s triggering these. Win 7

It’s infrequent enough that it’s not a huge issue, but when it happens it fires a bunch of them at the same time. Is there any way to simply make this silent and log it in an error log somewhere instead of throwing a bunch of alerts? I mean, how often do I really need to check GitHub now that I already have the packages? :smile:

Love the plugin though, blows every other IDE’s package management out of the water. Thanks for the hard work! :smile:[/quote]

Sorry for the long delay. Version 1.2.9 has handling built in to retry metadata requests that result in a 503. Hopefully this should reduce the number of popups you see.

0 Likes
#115

I upgraded my packages, got a load of popups, and now get this message when trying to start SublimeText. I no longer starts up :stuck_out_tongue:

http://dl.dropbox.com/u/497583/screenshots/SublimeText.png

That was using ST2 Build 2150. I’ve updated to Build 2151 but no change.

EDIT: Fixed it by following this https://forum.sublimetext.com/t/unable-to-run-package-setup/3350/4

0 Likes
#116

[quote=“firefusion”]I upgraded my packages, got a load of popups, and now get this message when trying to start SublimeText. I no longer starts up :stuck_out_tongue:

http://dl.dropbox.com/u/497583/screenshots/SublimeText.png

That was using ST2 Build 2150. I’ve updated to Build 2151 but no change.

EDIT: Fixed it by following this https://forum.sublimetext.com/t/unable-to-run-package-setup/3350/4[/quote]

Do you recall what the popups said?

Here are the instructions for future users to solve startup problems:

  1. Browse to your Installed Packages directory, which is one of the following:

  • Win: C:\Users{username}\AppData\Roaming\Sublime Text 2\Installed Packages\

  • OSX: /Users/{username}/Library/Application Support/Sublime Text 2/Installed Packages/

  • Linux: /home/{username}/.config/sublime-text-2/Installed Packages/

  1. Delete any .sublime-package files in there
  2. Start Sublime

This problem is caused by non-ascii filename being used in the package and the PackageSetup.py that comes with Sublime choking on it. I submitted a patch to Jon to fix some of these errors just a few days ago, but it looks like this is another. I’ll send him another patch to fix this.

0 Likes
#117

Thanks for the help

0 Likes
#118

Funny story.
I had installed SublimeCodeIntel again to give it another shot and maybe I would like it. It managed to slow my computer down and I decided to delete it. So I opened my packages folder and deleted it. I continue along for a couple of days and Sublime was giving me weird errors in the status bar. It said things like “Couldn’t find language” so I figured their was something wrong with my tmLanguage file or something. I opened up my console and saw a bunch of references to codeintel. I thought to myself, “That’s weird. I deleted that a while ago.” So I went to my packages and there it is again. So again I deleted it. I relaunch ST and all is well. Then the errors start coming back. I look at my console and it says, “orphaned file found. Package Control reinstalling SublimeCodeIntel.” So as it turns out, I needed to uninstall SublimeCodeIntel via Package Control.

TL;DR Package Control will reinstall packages that were deleted manually from the packages folder.

0 Likes
#119

this may already be known, but PC isn’t pulling the latest github version of SublimeCodeIntel. I noticed that in the json-package file for SublimeCodeIntel he hasn’t updated the version number or modified date, so I’m wondering if PC just looks for a change in that version number to know to update from github.

0 Likes
#120

This is on purpose. To make sure everyone is using the same version of SublimeCodeIntel (to help with debugging, etc.), Package Control uses the latest stable version of SublimeCodeIntel (as deemed by the developers of SublimeCodeIntel).

0 Likes
#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