Closed Massimo-B closed 11 years ago
In order to reproduce an error there is one thing you have to provide: your .vimrc. Contact me by irc or mail so that I can reproduce your issues on my virtual server. We'll find a fix fast then.
@MarcWeber Try checking it out without git in $PATH
.
@Massimo-B
my plugin_root_dir is /etc/vim/vim-addons.
a) Why?
b) Do you have permissions to write there (you should not unless you are working under root and you must not work under root as there are security issues in this case)?
I see everything is going fine until
curl: (37) Couldn't open file /etc/vim/vim-addons/vim-addon-manager-known-repositories-
. Much likely this is meaning that you don’t have permissions to write to /etc/vim/vim-addons
. Using VAM with plugin_root_dir set to not writable directory won’t ever be supported.
c) Why Github does not autocomplete your name when using @Mass…
a) Why not. I like to have a global VAM installation. I thought about setting my rtp to /usr/loca/share/vim or something. But then the global custom vimrc for gentoo is /etc/vim/vimrc.local so I put the add-ons there. Shouldn't matter.
b) I have. I would only Update the addons as root. The user should only have "read-only" access. For this issue here, the user is not involved. If this is going to work for users and if users vim add-ons are going to write there, I need to figure out...
$ ls -al /etc/vim/vim-addons
total 84K
drwxr-xr-x 21 root root 4,0K Jan 18 13:37 ./
drwxr-xr-x 4 root root 4,0K Jan 18 13:21 ../
drwxr-xr-x 7 root root 4,0K Jan 16 16:21 bash-support/
drwxr-xr-x 4 root root 4,0K Jan 18 13:24 BlockDiff/
drwxr-xr-x 9 root root 4,0K Jan 18 13:32 c%213/
drwxr-xr-x 8 root root 4,0K Jan 18 13:32 clang_complete/
drwxr-xr-x 4 root root 4,0K Jan 18 10:21 Distinguished/
drwxr-xr-x 5 root root 4,0K Jan 16 16:07 matchit.zip/
drwxr-xr-x 8 root root 4,0K Jan 16 16:26 perl-support/
drwxr-xr-x 7 root root 4,0K Jan 18 10:15 Powerline/
drwxr-xr-x 9 root root 4,0K Jan 17 16:19 snipmate/
drwxr-xr-x 4 root root 4,0K Jan 18 13:32 snipmate-snippets/
drwxr-xr-x 5 root root 4,0K Jan 18 13:23 SuperTab%1643/
drwxr-xr-x 5 root root 4,0K Jan 18 13:32 taglist/
drwxr-xr-x 7 root root 4,0K Jan 18 13:31 The_NERD_tree/
drwxr-xr-x 9 root root 4,0K Jan 18 13:10 tlib/
drwxr-xr-x 7 root root 4,0K Jan 16 14:27 vim-addon-manager/
drwxr-xr-x 3 root root 4,0K Jan 18 13:32 vim-addon-manager-known-repositories/
drwxr-xr-x 8 root root 4,0K Jan 18 13:32 vim-addon-manager-known-repositories-?/
drwxr-xr-x 5 root root 4,0K Jan 18 13:32 vim-addon-mw-utils/
drwxr-xr-x 4 root root 4,0K Jan 16 16:06 xml/
I cannot reproduce the issue when using non-git VAM-kr URL, it checkouts fine. Thus you need to check whom are you launching update from, error 37 means “FILE couldn't read file. Failed to open the file. Permissions?” (though on my system attempt to write to read-only directory returns error 23 “Write error. Curl couldn't write data to a local filesystem or similar.”). Though it is strange, it should’ve failed earlier (when creating new directory) if you did not have right permissions. Is it possible that something drops privileges of curl?
By the way,
I can't find why this path is created. Maybe due to my proxy adaption as proposed in your docs:
It is to preserve local changes, see :h VAM-do_diff
and :h VAM-hooks
.
Though it looks like it is being downloaded fine and without warnings (like “Failed to create the file /etc/tty”). Another idea: do you have enough space on device holding /etc
?
Massimo-B modified the VAM code always using the !executable('git') branch int vam.vim line 82. Thus this might be turned into a bug "why does updating VAM not work if you pretend to not have git". If somebody has this issue - I'll work on it. I'm lazy for now.
@MarcWeber Did I miss @Massimo-B posting his dotfiles? Anyway, it must work with both sources defined near line 82. In fact it works on my system, I don’t have much ideas how he could make it fail halfway with such weird message.
No, I talked to him by irc. Anyway, can be closed now
Hi,
my plugin_root_dir is /etc/vim/vim-addons. If there is no vim-addon-manager-known-repositories the update works. But if vim-addon-manager-known-repositories already exists it fails:
Afterwards it looks like this:
I can't find why this path is created. Maybe due to my proxy adaption as proposed in your docs: