Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while updating "minpac". Error code: 128 #51

Closed
Ferrodata opened this issue Feb 25, 2018 · 9 comments
Closed

Error while updating "minpac". Error code: 128 #51

Ferrodata opened this issue Feb 25, 2018 · 9 comments

Comments

@Ferrodata
Copy link

Ferrodata commented Feb 25, 2018

First of all, for several week I had no problems with minpac. All works fine until today:
Using neovim, try to run "PackageUpdate" and get the message: "Username for 'https://github.com': ". The status line shows error code 128 and neovim freeze. After I commented out all plugins and run "PackageClean" (no problems) I run "PackageUpdate" again. Now I got the error "Error plugins: 1".

This is my init.vim:

" PLUGINS
  packadd minpac
  call minpac#init()
   
  " minpac must have {'type': 'opt'} so that it can be loaded with `packadd`
 call minpac#add('k-takata/minpac', {'type': 'opt'})
  
 " Add other plugins here
 call minpac#add('vim-airline/vim-airline')
 "call minpac#add('mklabs/split-term.vim')
 "call minpac#add('tpope/vim-commentary')
 "call minpac#add('tpope/vim-dispatch')
 "call minpac#add('radenling/vim-dispatch-neovim')
 "call minpac#add('aimondi/delimitMate')
 "call minpac#add('vifm/neovim-vifm')
 
 command! PackUpdate call minpac#update()
 command! PackClean call minpac#clean()
@k-takata
Copy link
Owner

Error while updating "minpac". Error code: 128

This message is shown when the git command returns the error code 128, but I don't know what does it mean.
Do you see any other messages? Does :mes show anything else?

@Ferrodata
Copy link
Author

No, neovim freeze and after I restarted it, there are no messages available.

@gilacost
Copy link

gilacost commented Apr 8, 2018

Same problem 🤔

@gilacost
Copy link

gilacost commented Apr 9, 2018

@Ferrodata that error happens when you have any package name misspelled 🙋‍♂️ , cheers!

@jcronk
Copy link

jcronk commented May 8, 2018

I'm getting this same error, but it's not because the name is misspelled - I just verified that. What I do see when I go look, is that for some reason the git directory for the package is dirty, and I don't know why that would happen, and you can't just reset the working directory (because it's grafted? I don't know Git well enough to really know what that is). I've been able to resolve it by removing the package and then adding it again, but that's not ideal.

@alex-laties
Copy link

I'm currently getting this error with maralla/completer.vim.

My config, in its barest form, is:

call minpac#init({'verbose': 3})
call minpac#add('maralla/completer.vim')
packloadall

From the error messages, I get the following:

completer.vim: remote: Repository not found.
completer.vim: fatal: repository 'https://github.com/maralla/completer.vim.git/' not found
completer.vim:
Error while updating "completer.vim".  Error code: 128

It seems like minpac is appending a trailing slash currently to the repo URL currently.
https://github.com/maralla/completer.vim.git does exist, but https://github.com/maralla/completer.vim.git/ does not.

I'm currently running minpac at commit 9659ef5, which is latest master as of the time of this post.

@k-takata
Copy link
Owner

I consider to change the default value of 'verbose' from 1 to 2, so that users can easily check the reason of the error.

@alex-laties It seems that you misspelled the repository.
maralla/completer.vim should be maralla/completor.vim (er -> or).

@k-takata
Copy link
Owner

k-takata commented Sep 1, 2018

Now the default value of the 'verbose' option is changed to 2.
I hope that useful information is shown by that.

@k-takata
Copy link
Owner

k-takata commented Sep 1, 2018

Closing for now.

@k-takata k-takata closed this as completed Sep 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants