This bug was fixed in the package base-files - 12ubuntu4.1
---------------
base-files (12ubuntu4.1) jammy; urgency=medium
* /etc/os-release: add missing LTS to VERSION (LP: #1969960)
-- Paride Legovini <par...@ubuntu.com> Fri, 22 Apr 2022 16:34:19 +0200
** Changed in: base-files (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1969960
Title:
Jammy's /etc/os-release missing LTS string in VERSION
Status in base-files package in Ubuntu:
Fix Committed
Status in base-files source package in Jammy:
Fix Released
Bug description:
[Description]
In Jammy (base-files 12ubuntu4) we have:
$ grep VERSION= /etc/os-release
VERSION="22.04 (Jammy Jellyfish)"
but expected is:
VERSION="22.04 LTS (Jammy Jellyfish)"
Compare with Focal:
$ grep VERSION= /etc/os-release
VERSION="20.04.4 LTS (Focal Fossa)"
[Impact]
Having VERSION without LTS is inconsistent with the previous LTS
releases and is wrong, as the official name of the release is "22.04
LTS". This can confuse users.
Any script relying on VERSION to detect if the Ubuntu version it is
running on in an LTS won't be work as expected.
[Test Plan]
1. grep VERSION= /etc/os-release
2. check that it is: VERSION="22.04 LTS (Jammy Jellyfish)"
[Where problems could occur]
Software already packaged in Jammy may already have adapted to the
fact that VERSION doesn't have the LTS string in it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1969960/+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
