Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#7963 - syntax.vim not found, help does not work

Attached to Project: Arch Linux
Opened by SkippyleGrandGourou (SkippyleGrandGourou) - Thursday, 06 September 2007, 07:42 GMT
Last edited by Tobias Kieslich (tobias) - Monday, 21 January 2008, 19:27 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08 Don't Panic
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi,

Description:
Upgrading vim from ??? to 7.1.94 makes syntax.vim lost. Launching vim gives the message :
------------------------------------------------------
Error detected while processing /etc/vimrc:
line 41:
E484: Can't open file /usr/share/vim/syntax/syntax.vim
Press ENTER or type command to continue
------------------------------------------------------
There is no syntax.vim file in /usr/share/vim/* (but the 'syntax' directory is there and not empty).

The :help command does not work also (I had the idea to test it after reading an old (2004, fixed) bug report where both were declared not to work). The error is :
---------------------------------
E433: No tags file
E149: Sorry, no help for help.txt
---------------------------------


Additional info:
* package version(s) : 7.1.94, up to date standard distribution.


Steps to reproduce: upgrade vim, then launch it.
This task depends upon

Closed by  Tobias Kieslich (tobias)
Monday, 21 January 2008, 19:27 GMT
Reason for closing:  Works for me
Additional comments about closing:  I close it because I can not reproduce it anymore. If it was an issue, the wehn we move form the old vim/gvim layout to the new vi/vi/gvim layout.
Any fixes for that don't make sense anymore
Comment by Tobias Kieslich (tobias) - Thursday, 06 September 2007, 19:18 GMT
I can't reproduce that at all. I usually build at one box and upgrade the others by standard pacman -Syu. So on neither box I saw the issue.
Comment by SkippyleGrandGourou (SkippyleGrandGourou) - Thursday, 06 September 2007, 20:54 GMT
Well, I'm not sure about what is the reason, it appeared after a whole upgrade... Removing and reinstalling doesn't help.
Comment by Jens Adam (byte) - Friday, 07 September 2007, 01:18 GMT
Maybe try to temporarily rename/move your .vim* stuff?
Comment by SkippyleGrandGourou (SkippyleGrandGourou) - Friday, 07 September 2007, 05:47 GMT
Moving ~/.viminfo, /usr/share/vim or /etc/vimrc doesn't change anything (well, in the last case there is no more error message but the syntaxic coloration is still absent, of course).
Comment by SkippyleGrandGourou (SkippyleGrandGourou) - Saturday, 08 September 2007, 18:41 GMT
More info : I am upgrading another PC, and instead of "Suy-ing" I started by upgrading vim only. There is no problem. Here are some differences between the bugging version and the other one (both should come from the same repo) :

== buggy :
$ ls /usr/share/vim/
autoload indent plugin syntax
$ ls /usr/share/vim/syntax/ |wc -l
9
$ ls /usr/share/vim/syntax/
autohotkey.vim cdrtoc.vim coco.vim conaryrecipe.vim framescript.vim ldapconf.vim litestep.vim promela.vim voscm.vim
autoload indent plugin syntax

== normal :
$ ls /usr/share/vim/
autoload doc ftplugin.vim indent.vim macros plugin synmenu.vim vim16x16.gif vim32x32.xpm vimlogo.eps
bugreport.vim evim.vim ftplugof.vim indoff.vim makemenu.vim print syntax vim16x16.png vim48x48.gif vimlogo.gif
colors filetype.vim hi16-action-make.png keymap menu.vim rgb.txt termcap vim16x16.xpm vim48x48.png vimlogo.pdf
compiler ftoff.vim hi22-action-make.png lang mswin.vim scripts.vim tools vim32x32.gif vim48x48.xpm vimlogo.xpm
delmenu.vim ftplugin indent macmap.vim optwin.vim spell tutor vim32x32.png vimlogo.cdr vimrc_example.vim
$ ls /usr/share/vim/syntax/ | wc -l
500

I'll try to upgrade step by step, in order to see if another package can be the cause of this weird behaviour...
Comment by SkippyleGrandGourou (SkippyleGrandGourou) - Monday, 01 October 2007, 20:01 GMT
Ok. I've just tried to find what was wrong. Syntax and help stuff are not located in vim package but in vi. Although vi seemed up-to-date, reinstalling it with a cleared cache did the trick. Maybe the archive was corrupted, or whatever...

Anyway, this task can be closed since I don't think it is a bug, but a local problem from my computer. Sorry for disturbance...
Comment by Steve H. (ryz) - Monday, 26 November 2007, 18:52 GMT
I can confirm this problem, i've got exactly the same error message after upgrading my box with 'pacman -Syu'.

I'm going to follow the steps SkippyleGrandGourou posted.

But: Maybe still a bug after all?
Comment by Aaron Griffin (phrakture) - Monday, 26 November 2007, 18:54 GMT
Reopening for my sanity.

If two people have this problem, there might be something wrong here... it appears related to an upgrade of 'vi' ? I can't reproduce it thought - did you guys happen to uninstall vi, by chance?
Comment by Tobias Kieslich (tobias) - Thursday, 10 January 2008, 19:35 GMT
I still can't reproduce it, I tried doing incremental upgrades and stuff, but it never lost files served by vi
Comment by Mark DeVries (mdevries) - Friday, 11 January 2008, 18:12 GMT
I had the exact same issue after a pacman -Syu. Reinstalling vi fixed the problem. This was an old development machine that had not been upgraded since February of last year.
Comment by Tobias Kieslich (tobias) - Friday, 18 January 2008, 03:05 GMT
it might have happened that one of the vim package does not had no dependency on vi (version restricted), but still I' don't see where the issue came from.
Comment by Steve H. (ryz) - Friday, 18 January 2008, 07:47 GMT
As already said, reinstalling vi fixed the problem.
Comment by Aaron Griffin (phrakture) - Friday, 18 January 2008, 18:09 GMT
I say we close this 8)

Loading...