-
Notifications
You must be signed in to change notification settings - Fork 296
"apm list -b" and "apm i --packages-file" are incompatible with git packages #867
Comments
Thanks for opening a new issue and for sharing those repro steps 👍 I can reproduce on macOS 10.14.6 with Atom 1.40.1. I temporarily reset to factory defaults and then followed your steps and see the same error though I'm still not sure why my attempt to reproduce using defunkt/zen didn't reproduce (/cc #833 (comment))? |
I think the difference is that zen is actually a "normal" (I don't know the right name, sorry) package, ie. is listed on atom.io (https://atom.io/packages/zen) and the repo is for development or something, so you can actually install from it (it has version tags, so it also get the correct version) but when On the other hand ghost-text isn't listed (https://atom.io/packages/search?q=ghost-text), so apm can't find it. Simply speaking: I can do |
Hello Thanks for the clarifications. |
Maybe a some details of my issue would help here My issueI’m exporting the list of my packages with :
then try to install this list with: My current workaround with Powershell,Is to clean up my-packages.txt
Then install with
|
Prerequisites
Description
I'm trying to back up Atom installed packages with
apm list -ib
, and I expected the output of this command to be compatible withapm install --packages-file
, but this isn't the case if there are git packages installed.This issue is a lot like #833, but that's closed so I opened another one as stated here.
I would like to be able to do
and then
but this produces an error when apm tries to install a git package.
Steps to Reproduce
apm i GhostText/GhostText-for-Atom
apm list -ib > atom-packages.list
This file now contains only the single line
ghost-text@0.0.1
apm i --packages-file atom-packages.list
Expected behavior:
I expect it to smoothly install GhostText/GhostText-for-Atom.
Actual behavior:
It throws the following error:
Versions
The system is Lubuntu 19.04, linux kernel 5.0.0-13-generic
The text was updated successfully, but these errors were encountered: