Description of problem: updating to vim 7.3.515-1 (vim-common, vim-enhanced, vim-filesystem, vim-minimal) results in sudoedit not working, for example see following command $ sudoedit /etc/hosts sudoedit: /bin/vi: command not found Version-Release number of selected component (if applicable): 7.3.515-1 How reproducible: always Steps to Reproduce: 1. update vim to version 7.3.515-1 (from 7.3.315-1) Actual results: enter: sudoedit filename get: sudoedit: /bin/vi: command not found" Expected results: file opens for editing in vim Additional info: downgrading to version 7.3.315-1 makes it work properly again
I see it breaks because vim-minimal x86_64 2:7.3.515-1.fc16 package now puts vi in /usr/bin, I guess because of new f17 filesystem where /bin is just a link to /usr/bin. new version of vim-minimal works if i do "ln -s /usr/bin/vi /bin/vi" maybe vim-minimal package for f16 should either make a link to new location of vi or install it in /bin unless f16 filesystem is also going to change.
Not just symlinks to vi but vi need symlinks for other files as well. Because there may other programs which depend on ex or rvi or rview or view. This should fix it: cd /bin ln -s ../usr/bin/vi ln -s vi ex ln -s vi rvi ln -s vi rview ln -s vi view
Please read earlier comment as: Not just symlink for /bin/vi to /usr/bin/vi, but we need symlinks for other files as well. ...
vim-7.3.515-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/vim-7.3.515-2.fc16
Package vim-7.3.515-2.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing vim-7.3.515-2.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-8354/vim-7.3.515-2.fc16 then log in and leave karma (feedback).
vim-7.3.515-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.