** Description changed: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog - 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. + 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 Lunar archive, and open the changelog with Vim. Instead of the changelog - release (e.g. "lunar") showing as red, it should show as blue. + release (e.g. "lunar") showing as red, it should show as blue. I would + also suggest editing sources.list, to ensure e.g. Eoan shows as EOL.
-- 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/1996087 Title: Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Committed Status in vim source package in Focal: Confirmed Status in vim source package in Jammy: Confirmed Status in vim source package in Kinetic: Confirmed Status in vim source package in Lunar: Fix Committed Bug description: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. 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 Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "lunar") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1996087/+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
