Sublime Forum

Can't install new packages on build 3126

#8

It seems it is in read-only mode. (thanks for helping out, btw):

{
	// A list of URLs that each contain a JSON file with a list of repositories.
	// The repositories from these channels are placed in order after the
	// repositories from the "repositories" setting
	"channels": [
		"https://packagecontrol.io/channel_v3.json"
	],

	// A list of URLs that contain a packages JSON file. These repositories
	// are placed in order before repositories from the "channels"
	// setting
	"repositories": [],

	// A list of packages to install pre-release versions for. Versions
	// under 1.0.0 are not considered pre-release, only those using the SemVer
	// -prerelease suffixes will be ignored if the package is not in this
	// list.
	"install_prereleases": [],

	// If debugging information for HTTP/HTTPS connections should be printed
	// to the Sublime Text console
	"debug": false,

	// This helps solve naming issues where a repository it not named the
	// same as the package should be. This is primarily only useful for
	// GitHub and BitBucket repositories. This mapping will override the
	// mapping that is retrieved from the repository channels.
	"package_name_map": {},

	// If package install, upgrade and removal info should be submitted to
	// the channel for aggregated statistics
	"submit_usage": true,

	// The URL to post install, upgrade and removal notices to
	"submit_url": "https://packagecontrol.io/submit",

	// If packages should be automatically upgraded when ST starts
	"auto_upgrade": true,

	// If missing packages should be automatically installed when ST starts
	"install_missing": true,

	// If a package was installed by Package Control (has a
	// package-metadata.json file) but is not in installed_packages, remove it
	// based upon the assumption that it was removed on another machine and
	// the Package Control.sublime-settings file was synced to this machine.
	"remove_orphaned": true,

	// The minimum frequency in hours in which to check for automatic upgrades,
	// setting this to 0 will always check for automatic upgrades
	"auto_upgrade_frequency": 1,

	// Packages to not auto upgrade
	"auto_upgrade_ignore": [],

	// Timeout for downloading channels, repositories and packages. Doesn't
	// have an effect on Windows due to a bug in WinINet.
	"timeout": 30,

	// The number of seconds to cache repository and package info for
	"cache_length": 300,

	// An HTTP proxy server to use for requests. Not normally used on Windows
	// since the system proxy configuration is utilized via WinINet. However,
	// if WinINet is not working properly, this will be used by the Urllib
	// downloader, which acts as a fallback.
	"http_proxy": "",
	// An HTTPS proxy server to use for requests - this will inherit from
	// http_proxy if it is set to "" or null and http_proxy has a value. You
	// can set this to false to prevent inheriting from http_proxy. Not
	// normally used on Windows since the system proxy configuration is
	// utilized via WinINet. However, if WinINet is not working properly, this
	// will be used by the Urllib downloader, which acts as a fallback.
	"https_proxy": "",

	// Username and password for both http_proxy and https_proxy. May be used
	// with WinINet to set credentials for system-level proxy config.
	"proxy_username": "",
	"proxy_password": "",

	// If HTTP responses should be cached to disk
	"http_cache": true,

	// Number of seconds to cache HTTP responses for, defaults to one week
	"http_cache_length": 604800,

	// User agent for HTTP requests. If "%s" is present, will be replaced
	// with the current version.
	"user_agent": "Package Control v%s",

	// A list of package names to ignore when performing operations. This will
	// only affect packages that appear to be a git or hg repository, but will
	// be especially useful for package developers who manually deal with the
	// repository and don't want Package Control touching it.
	//
	// It can help if trying to list packages to install hangs, possibly due
	// to an interactive prompt.
	//
	// The setting can also be set to the boolean true to ignore all git and hg
	// repositories, no matter what the name.
	"ignore_vcs_packages": [],

	// Custom path(s) to "git" binary for when it can't be automatically
	// found on the system and a package includes a .git metadata directory.
	// Supports more than one path to allow users to sync settings across
	// operating systems.
	"git_binary": [],

	// This should NOT contain the name of the remote or branch - that will
	// be automatically determined.
	"git_update_command": ["pull", "--ff", "--commit"],

	// Custom path(s) to "hg" binary for when it can't be automatically
	// found on the system and a package includes a .hg metadata directory.
	// Supports more than one path to allow users to sync settings across
	// operating systems.
	"hg_binary": [],

	// For HG repositories, be sure to use "default" as the remote URL.
	// This is the default behavior when cloning an HG repo.
	"hg_update_command": ["pull", "--update"],

	// Additional packages to ignore when listing unmanaged packages.
	"unmanaged_packages_ignore": [],

	// The downloader backends that should be used for HTTP(S) requests, split
	// by operating system to allow for configuration to be shared.
	//
	// Valid options include: "urllib", "curl", "wget", (Windows-only) "wininet"
	//
	// This setting allows Windows users to bypass wininet and use urllib
	// instead if they machine or network presents trouble to wininet. Some
	// OS X and Linux users have also reported better luck with certain proxies
	// using curl or wget instead of urllib.
	//
	// The "curl" and "wget" options require the command line "curl" or "wget"
	// program installed and present in the PATH.
	"downloader_precedence": {
		"windows": ["wininet"],
		"osx": ["urllib"],
		"linux": ["urllib", "curl", "wget"]
	},

	// Directories to ignore when creating a package
	"dirs_to_ignore": [
		".hg", ".git", ".svn", "_darcs", "CVS"
	],

	// Files to ignore when creating a package
	"files_to_ignore": [
		"*.pyc", ".hgignore", ".gitignore", ".bzrignore",
		"*.sublime-project", "*.sublime-workspace", "*.tmTheme.cache"
	],

	// Files to include, even if they match a pattern in files_to_ignore
	"files_to_include": [],

	// When a package is created, copy it to this folder - defaults to Desktop
	"package_destination": "",

	// A way to create different packaging profiles for different types of
	// package releases, such as for different platforms or binary-only
	// releases.
	//
	// The key of the object will be the profile name and a list of them will
	// be presenting when running the "Create Package File" command. The
	// profile "Default" will use the top-level version on the following
	// settings:
	//
	// - "dirs_to_ignore"
	// - "files_to_ignore"
	// - "files_to_include"
	// - "package_destination"
	//
	// If a profile does not include one of those three setting, it will fall
	// back to the top-level settings.
	"package_profiles": {
		"Binaries Only": {
			// Exclude all .py files, but consequently include all .pyc files
			"files_to_ignore": [
				"*.py", ".hgignore", ".gitignore", ".bzrignore",
				"*.sublime-project", "*.sublime-workspace", "*.tmTheme.cache"
			],

			// Include __init__.py so Sublime Text will load the package
			"files_to_include": [
				"__init__.py"
			]
		}
	},

	// Enable the ability to run the tests - this is only for development
	"enable_tests": false
}
0 Likes

#9

That looks like the default settings. I need the contents of Packages/User/Package Control.sublime-settings, which contains your user settings. That file won’t have any comments in it since it is written programatically.

0 Likes

#10
{
	"bootstrapped": true,
	"debug": true,
	"in_process_packages":
	[
		"0_package_control_loader",
		"All Autocomplete",
		"Autoprefixer",
		"Awk",
		"ColorPicker",
		"GitGutter-Edge",
		"HTML Snippets",
		"HTML5",
		"LESS",
		"Material Theme",
		"React Development Snippets",
		"React Templates",
		"ReactJS",
		"Terminal"
	],
	"installed_packages":
	[
		"Alignment",
		"Babel",
		"Expand Tabs on Save",
		"Facebook Material Theme",
		"Git",
		"GitGutter-Edge",
		"Material Color Scheme",
		"Material Theme",
		"Material Theme - White Panels",
		"Oceanic Color Scheme",
		"Oceanic Next Italic Color Scheme",
		"Package Control",
		"React ES6 Snippets",
		"Sass",
		"Theme - Dark Material"
	]
}
0 Likes

#11

Should I start thinking about a clean install?

0 Likes

#12

You are right, however the package control seens very robust. I do not recall much problems with it, and I like 5 in minutes may completely install/reinstall all my settings and package whatever I go, without any problems. But if you want to make it more robust, add a new simple feature:

Just because something is failing, why break everything else. And also, this looks the error:

File "package_control.settings in /Users/me/Library/Application Support/Sublime Text 3/Installed Packages/Package Control.sublime-package", line 73, in <lambda>
AttributeError: 'int' object has no attribute 'lower'

You did not do this already? You are too patient. I would do it on the first minutes its starts troubling. And I recommend you to apply version control over your settings, this way you may move to other computers at speed light. Also, do clean install as well. Note, there is one you would like to backup also, and I do not mentioned at my previous post, is the file, BACKUP_FOLDER/Local/Session.sublime_session, to your new clean install YOUR_DATA_FOLDER/Local/Session.sublime_session. The Session.sublime_session file contains all your current/recent projects/workspaces, and etc. You are welcome to open it, and edit as you like to clean or personalize it.

0 Likes

#13

I’ve started the clean install process following your procedure.
Now at step 5. It does seem like it finished reinstalling package control but it never asked to restart. Feels like restarting anyway. What do you think?

0 Likes

#14

Are you following the steps? Restart does not kill, and is fast to do. For my experience, when installing things any where, a restart is good.

0 Likes

#15

Does not work. Yet. One of my packages throws an error and keeps Sublime from installing all the other packages.

0 Likes

#16

Remove that package form the list. And let it install all the others. What is the console output? It seens a problem with that package. Open a issue on its github issue tracker.

0 Likes

#17

Oh now this:
Error trying to parse settings: Unexpected newline in Packages/User/Package Control.sublime-settings:19:3

0 Likes

#18

Show your Package Control.sublime-settings file contents.

0 Likes

#19

There is no newline in the file unless TextEdit adds a newline automatically after saving.

{
	"bootstrapped": true,
	"installed_packages":
	[
		"Alignment",
		"Babel",
		"Expand Tabs on Save",
		"Facebook Material Theme",
		"Git",
		"GitGutter-Edge",
		"Material Color Scheme",
		"Material Theme",
		"Material Theme - White Panels",
		"Oceanic Color Scheme",
		"Oceanic Next Italic Color Scheme",
		"Package Control",
		"React ES6 Snippets",
		"Sass",
		"Theme - Dark Material”,
		"0_package_control_loader",
		"All Autocomplete",
		"Autoprefixer",
		"Awk",
		"ColorPicker",
		"GitGutter-Edge",
		"HTML Snippets",
		"HTML5",
		"React Development Snippets",
		"React Templates",
		"ReactJS",
		"Terminal"
	]
}
0 Likes

#20

Change this to this " on the line "Theme - Dark Material”,.

1 Like

#21

You do have falcon eyes.
Worked. Thanks.

0 Likes

#22

It’s a Package control issue.
Follow steps described in the link. It worked for me
https://packagecontrol.io/docs/troubleshooting#Purging_and_Reinstalling

1 Like

#23

This worked for me …been struggling with it since so long…thanks

1 Like

#24

I am going to try to fix whatever I wrote there:

You are right, however the package control is very robust. I do not recall much problems with it, and in about 5 in minutes Package Control should be able to completely reinstall all my settings and packages without any problems except maybe for this:
https://github.com/wbond/package_control/issues/1191

Sorry for this last part, I just have no ideia what it does mean.

Some years ago I had written these steps on how to do a complete clean install, but the old post nowadays does not seem very well structured. Then, I tried to rewritten a little these steps. Anyone new having problems can either try to revert everything at once, or do a few packages or settings at a time. This way you should be able to know if there is some Sublime Text package causing this problem.

Try following the steps from https://www.sublimetext.com/docs/3/revert.html and see if it fixes the problem. If reversing Sublime Text to a clean state fixes the problem, then, you can try gradually to reinstall all your Sublime Text packages in hope to figure out what packages could be causing the problem:

  1. Close Sublime Text.
  2. Backup your whole Sublime Text data directory. (see here where your data directory is)
  3. Delete all contents from your data directory.
  4. Open Sublime Text and install back Package Control: https://packagecontrol.io/installation
    • Wait it be completely installed (some times it ask you to restart 1 or several times, then just do it until finish all restarts).
  5. Close Sublime Text.
  6. Inside your data directory, create the directory YOUR_DATA_FOLDER/Packages/User, if it already does not exists.
  7. From your Sublime Text data backup directory, copy the following directory contents:
    BACKUP_FOLDER/Packages/User to YOUR_DATA_FOLDER/Packages/User
    • If coping everything at once does not solve the problem, try to do this one settings by one, so you know what package could be causing the problem.
  8. Open the file YOUR_DATA_FOLDER/Packages/User/Package Control.sublime-settings (not use Sublime Text to edit).
    • Check if there are some packages on the in_process_packages array. If so, remove the packages from the “in_process_packages” array:

         {
             "bootstrapped": true,
             "in_process_packages":
             [
                 "SomeOtherPackage"
             ],
             "installed_packages":
             [
                 "Package Control"
             ]
         }
      
    • And add them to the "installed_packages" array:

         {
             "bootstrapped": true,
             "in_process_packages":
             [
             ],
             "installed_packages":
             [
                 "Package Control",
                 "SomeOtherPackage",
             ]
         }
      
    • Do not forget to add a trailing comma after the last package name on the array "installed_packages", before merging them. If the array "installed_packages" does not exist in your Package Control.sublime-settings, just create one like the above example.

    • If installing all packages at once does not solve the problem, try to do this one package by one, so you know what package could be causing the problem.

  9. Open Sublime Text and Package Control should start installing all your packages.
0 Likes

#25

Hi, I’m still struggling to install packages even with all this help. Here is my Package Control.sublime-settings:
{
“bootstrapped”: true,
“in_process_packages”:
[
“Predawn”
],
“installed_packages”:
[
“Package Control”,
“Predawn”
]
}
and my Preferences.sublime-settings:
{
“ignored_packages”:
[
“Vintage”
]
}
This is what the console tells me:
Package Control: Error downloading package. HTTP exception InvalidCertificateException (Host codeload.github.com returned an invalid certificate ([SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:548))) downloading https://codeload.github.com/jamiewilson/predawn/zip/2.0.5.
error: Package Control

This error has happened with every package I have attempted to install so far (this has also included SideBarEnhancements, for reference).

0 Likes

#26

Sorry - I did delete “Predawn” from in_process_packages before I ran this, so assume that there are no in process packages when I get this error.

0 Likes

#27

What version of Sublime Text are you using?

0 Likes