LVLAaron Posted February 1, 2013 Share Posted February 1, 2013 I just rebuilt a new unraid system (4.7) and needed VIM.... unMENU tells me: Installed, but version is different. Current version='' expected '7.2' So I tried a manual install: root@Tower:/boot/packages# installpkg vim-7.2.416-i486-1.txz Verifying package vim-7.2.416-i486-1.txz. Installing package vim-7.2.416-i486-1.txz: PACKAGE DESCRIPTION: # vim (Vi IMproved) # # Vim is an almost compatible version of the UNIX editor vi. Many new # features have been added: multi level undo, command line history, # filename completion, block operations, and more. # # Vim's development is led by Bram Moolenaar. # # This package also contains the Exuberant Ctags program # written by Darren Hiebert. # Executing install script for vim-7.2.416-i486-1.txz. Package vim-7.2.416-i486-1.txz installed. root@Tower:/boot/packages# vim vim: /lib/libc.so.6: version `GLIBC_2.11' not found (required by vim) Saw another user.... his thread title wasn't the best, so I started this thread: http://lime-technology.com/forum/index.php?topic=17180.0 Quote Link to comment
Joe L. Posted February 1, 2013 Share Posted February 1, 2013 I just rebuilt a new unraid system (4.7) and needed VIM.... unMENU tells me: Installed, but version is different. Current version='' expected '7.2' So I tried a manual install: root@Tower:/boot/packages# installpkg vim-7.2.416-i486-1.txz Verifying package vim-7.2.416-i486-1.txz. Installing package vim-7.2.416-i486-1.txz: PACKAGE DESCRIPTION: # vim (Vi IMproved) # # Vim is an almost compatible version of the UNIX editor vi. Many new # features have been added: multi level undo, command line history, # filename completion, block operations, and more. # # Vim's development is led by Bram Moolenaar. # # This package also contains the Exuberant Ctags program # written by Darren Hiebert. # Executing install script for vim-7.2.416-i486-1.txz. Package vim-7.2.416-i486-1.txz installed. root@Tower:/boot/packages# vim vim: /lib/libc.so.6: version `GLIBC_2.11' not found (required by vim) Saw another user.... his thread title wasn't the best, so I started this thread: http://lime-technology.com/forum/index.php?topic=17180.0 There's the reason, a missing library it depends on. /lib/libc.so.6: version `GLIBC_2.11' not found I'd look for a different package for "vim" anf not mess with libc.so.8, as it is used by most everything, and is you put a different version into place, who knows what will break. You sure you need "VIM" as "vi" is stock with unRAID? Joe L. Quote Link to comment
LVLAaron Posted February 2, 2013 Author Share Posted February 2, 2013 Right, I can see the problem; but I wanted to let whoever handles the unMENU stuff to know that their package is broken.... But yes, I prefer VIM because I don't know the key bindings, etc for VI. Quote Link to comment
Joe L. Posted February 2, 2013 Share Posted February 2, 2013 Right, I can see the problem; but I wanted to let whoever handles the unMENU stuff to know that their package is broken.... But yes, I prefer VIM because I don't know the key bindings, etc for VI. unless you are doing something VIM specific, the commands are the same. VIM is a superset of vi. Quote Link to comment
LVLAaron Posted February 2, 2013 Author Share Posted February 2, 2013 The key bindings are NOT the same. That's not the point of this thread anyway. The point is, there is something that is "broken" in unMENU. Quote Link to comment
Joe L. Posted February 2, 2013 Share Posted February 2, 2013 The key bindings are NOT the same. That's not the point of this thread anyway. The point is, there is something that is "broken" in unMENU. I suspect it will stay broken... unless the person who contributed that package updates it. It certainly worked at one time with an older version of unRAID. I grew up with UNIX (over 30+ years) and every version of vi I've ever used had the same basic abilities and key mappings. I even learned enough of "emacs" to be able to survive when on a BSD machine... You think vim->vi key mappings are tough... wrong... try vi->emacs. You are more than welcome to contribute instead of criticize, and fix the VIM package for the benefit of others like you who can't do without the key-bindings you so dearly miss. Odds are the existing package is for an older version of VIM regardless. Joe L. Quote Link to comment
LVLAaron Posted February 2, 2013 Author Share Posted February 2, 2013 Yeah, ease up. I'm not criticizing anything. I'm mainly wanted to let people know, in case they also want to use the same package.... Quote Link to comment
Joe L. Posted February 2, 2013 Share Posted February 2, 2013 Yeah, ease up. I'm not criticizing anything. I'm mainly wanted to let people know, in case they also want to use the same package.... try this version... it seems to work for me: http://search.slackware.eu/cgi-bin/package.cgi/view/slackware-13.37/slackware/ap/vim-7.3.154-i486-1.txz install with installpkg vim-7.3.154-i486-1.txz Quote Link to comment
LVLAaron Posted February 2, 2013 Author Share Posted February 2, 2013 I tried that, too. Same message about glibc. I went back and pulled the glibc and vim packages from my previous working install and I'm still having the issue. The dependency must have been satisfied by something else that I had installed/running. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.