Public bug reported: In several stable releases of Ubuntu, Vim needs accurate information about Ubuntu and Debian codenames. This information should be aligned with what is in distro-info-data.
There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Plucky archive, and open the changelog with Vim. Instead of the changelog release (e.g. "plucky") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Kinetic shows as EOL. ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Affects: vim (Ubuntu Focal) Importance: Undecided Status: New ** Affects: vim (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: vim (Ubuntu Noble) Importance: Undecided Status: New ** Affects: vim (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: vim (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: vim (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: vim (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: vim (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2084706 Title: Add Plucky as a known Ubuntu distribution Status in vim package in Ubuntu: New Status in vim source package in Focal: New Status in vim source package in Jammy: New Status in vim source package in Noble: New Status in vim source package in Oracular: New Bug description: In several stable releases of Ubuntu, Vim needs accurate information about Ubuntu and Debian codenames. This information should be aligned with what is in distro-info-data. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Plucky archive, and open the changelog with Vim. Instead of the changelog release (e.g. "plucky") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Kinetic shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2084706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp