Bug 503429 - ViM files for lilypond installed in the wrong location
Summary: ViM files for lilypond installed in the wrong location
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lilypond
Version: 11
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-01 01:26 UTC by Byron Clark
Modified: 2009-06-24 19:36 UTC (History)
2 users (show)

Fixed In Version: 2.11.57-2.fc9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-24 19:17:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Byron Clark 2009-06-01 01:26:30 UTC
Description of problem:
ViM files for lilypond are installed in /usr/share/vim/vim71 so ViM 7.2 doesn't see them.  The files should be installed in /usr/share/vim/vim72.

Version-Release number of selected component (if applicable):
lilypond-2.12.2-3.fc11.x86_64
vim-enhanced-7.2.148-1.fc11.x86_64

Comment 1 Gwyn Ciesla 2009-06-01 14:07:18 UTC
Am I correct in seeing that vim 7.2 is in everything from rawhide back to F-9?

Comment 2 Bug Zapper 2009-06-09 16:54:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Byron Clark 2009-06-15 16:06:47 UTC
(In reply to comment #1)
> Am I correct in seeing that vim 7.2 is in everything from rawhide back to F-9?  

That seems to be the case.

Comment 4 Fedora Update System 2009-06-15 17:26:29 UTC
lilypond-2.12.0-2.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/lilypond-2.12.0-2.fc10

Comment 5 Fedora Update System 2009-06-15 17:26:34 UTC
lilypond-2.12.2-4.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/lilypond-2.12.2-4.fc11

Comment 6 Fedora Update System 2009-06-15 17:26:38 UTC
lilypond-2.11.57-2.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/lilypond-2.11.57-2.fc9

Comment 7 Fedora Update System 2009-06-18 11:40:39 UTC
lilypond-2.11.57-2.fc9 has been pushed to the Fedora 9 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing-newkey update lilypond'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2009-6528

Comment 8 Fedora Update System 2009-06-18 11:53:18 UTC
lilypond-2.12.0-2.fc10 has been pushed to the Fedora 10 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update lilypond'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-6630

Comment 9 Fedora Update System 2009-06-18 11:55:34 UTC
lilypond-2.12.2-4.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update lilypond'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-6653

Comment 10 Fedora Update System 2009-06-24 19:17:48 UTC
lilypond-2.12.2-4.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2009-06-24 19:19:00 UTC
lilypond-2.12.0-2.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2009-06-24 19:36:02 UTC
lilypond-2.11.57-2.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.