Bug 2124183 - lilypond syntax files should be packaged for vim 9.0 but are still for vim 8.0
Summary: lilypond syntax files should be packaged for vim 9.0 but are still for vim 8.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lilypond
Version: 36
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-05 07:32 UTC by Martin Tarenskeen
Modified: 2022-09-28 12:10 UTC (History)
2 users (show)

Fixed In Version: lilypond-2.23.12-2.fc37 lilypond-2.23.13-1.fc36
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-14 00:20:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Martin Tarenskeen 2022-09-05 07:32:41 UTC
Description of problem:
vim syntax files in lilypond package are for vim 8.2 while Fedora 36+ already has vim 9.0 now

Version-Release number of selected component (if applicable):
lilypond-2.23.12-1.fc36.x86_64

How reproducible:
always

Steps to Reproduce:
1. rpm -ql lilypond | grep vim
2. rpm -ql vim-common | grep share 

Actual results:
1. /usr/share/vim/vim82/*
2. /usr/share/vim/vim90/*


Expected results:
1. /usr/share/vim/vim90/*
2. /usr/share/vim/vim90/*

Comment 1 Fedora Update System 2022-09-06 21:39:21 UTC
FEDORA-2022-e72a7795f7 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e72a7795f7

Comment 2 Fedora Update System 2022-09-06 21:39:22 UTC
FEDORA-2022-4803fe1c76 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4803fe1c76

Comment 3 Fedora Update System 2022-09-07 07:38:42 UTC
FEDORA-2022-4803fe1c76 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-4803fe1c76`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4803fe1c76

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2022-09-07 10:50:58 UTC
FEDORA-2022-e72a7795f7 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-e72a7795f7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e72a7795f7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2022-09-14 00:20:30 UTC
FEDORA-2022-4803fe1c76 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2022-09-14 02:40:30 UTC
FEDORA-2022-2cd31d7e2b has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-2cd31d7e2b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-2cd31d7e2b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-09-20 01:38:32 UTC
FEDORA-2022-ab73daed47 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-ab73daed47`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ab73daed47

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-09-28 12:10:38 UTC
FEDORA-2022-ab73daed47 has been pushed to the Fedora 36 stable repository.
If problem still persists, 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.