-
Notifications
You must be signed in to change notification settings - Fork 17.4k
Unable to Install Certain Packages #5202
Comments
You need to install git. If you're on Windows, type "Git for Windows" in Google, it's the first result. Beware, when i tried opening the git installer ti seemed to hang. Apparently "doing stuff" makes it work, so just browse the web for a few minutes and you'll eventually get the installer to pop up... It was weird. You will also need to close and reopen Atom once git is installed. Finally, make sure to select the option to add git to your PATH variable. (the middle option, where it says "considered safe") |
I already have git. WIth Github for windows, plus I can install other packages, that as far as i can tell don't have the harmony-collections package. I may be wrong about that part though. |
Is git in your PATH?
|
Yes it is |
@karai17: This issue is not because Git is missing (if it was, the error log would clearly state so). It looks more like something went wrong when storing the files. |
I've got the same error today on Windows 7 x64 with atom 0.175.0 when I tried to install atom-beautify package.
|
I also have this problem and cannot install and update packages. Log for linter package:
Log for terminal-panel package:
Windows 8.1 x64, Atom 0.175.0, Git 2.2.2 in PATH. |
Has anyone tried releases of atom before 0.175? This was the first upgrade for me in over a month when this issue showed up. I can try going back a couple revisions, just for curiousity sake. |
Ooops. I missed this and posted this issue on atom/apm atom/apm#274 Should I close that issue? |
Looks like this may have been fixed in a recent npm build, npm/npm#7083 |
Yeah, I think that makes sense since this issue has traction even though it is an apm issue. |
I just installed 0.173 atom and packages that previously failed to install, now install. |
How does one install old versions? On Fri, Jan 23, 2015 at 4:19 PM, Lucas Brendel notifications@github.com
|
@mark-hahn I just ran an uninstall of atom 0.175 and then downloaded the 0.173 build. My previous packages that were installed stayed so i didn't have to reinstall them. If you aren't using the Atom installer and instead the zip version, i am guessing deleting the atom directory would work. |
I should make a correction. I downgraded to 0.174, not 0.173 |
Comment deleted. |
How does one install old versions? I came across Atom for the first time today and I too can't install packages because their path names are monstrously long. |
See #5109. On Sat, Jan 24, 2015 at 12:51 PM, RichardJECooke notifications@github.com
|
I got the same issue trying to install the minimap package after just upgrading to Atom 0.175.0. I'm running Windows 7 64-bit.
|
Can anyone who's not on Windows reproduce this? It looks like it's a Windows-specific bug at this point. |
@kevinsawicki: Could this have been caused by #5175? |
I've got fixed this on my machine by upgrading local git version from 1.8.4.msysgit.0 to the latest one for Windows - 1.9.5.msysgit.0. Now I am able to install packages correctly. |
Thank you very much. This was killing me. I couldn't even test the On Sun, Jan 25, 2015 at 11:35 PM, Aliaksei Varabei <notifications@github.com
|
Thanks, this resolved this issue for me. A possible fix for the issue permanently would be a recommendation message to upgrade git if this error occurs in Atom. |
I don't think so, I believe this was caused by the npm upgrade in atom/apm#252 |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks! |
I update my atom install going from the previous zip download, wiping all that away and using the new installer, but now certain packages won't install.
Here is my error output from the install command
I have gotten Themes and some packages, like color-picker to install but most fail and it is this same error.
Is this more an NPM issue? I have looked at other issues but none seemed to throw this error.
The text was updated successfully, but these errors were encountered: