From: Zbigniew Jędrzejewski-Szmek Date: Wed, 6 Jul 2022 15:19:27 +0000 (+0200) Subject: os-release: define SUPPORT_END= X-Git-Tag: v252-rc1~717 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2615c1f17ab1768ebe015d0719cc1ee2e6b092f1;p=thirdparty%2Fsystemd.git os-release: define SUPPORT_END= Fixes #21764. I think is very simple, but flexible. The date may be set early, for distros that have a fixed schedule, but it doesn't have to. So for example Debian could push out an update that sets a few months before the release goes EOL. And various tools, in particular graphical desktops, can start nagging people to upgrade a few weeks before the date. As discussed in the bug, we don't need granularity higher than a day. And this means that we can use a simple human- and machine-readable format. I was considering other names, e.g. something with "EOL", but I think that "SUPPORT_END" is better because it doesn't imply that the machine will somehow stop working. This is supposed to be an advisory, nothing more. --- diff --git a/man/os-release.xml b/man/os-release.xml index 90527228a23..fd98be5b7a3 100644 --- a/man/os-release.xml +++ b/man/os-release.xml @@ -350,6 +350,16 @@ BUG_REPORT_URL="https://bugzilla.redhat.com/". + + SUPPORT_END= + + The date at which support for this version of the OS ends. (What exactly "lack of + support" means varies between vendors, but generally users should assume that updates, including + security fixes, will not be provided.) The value is a date in the format + YYYY-MM-DD, and specifies the last day on which support is + provided. + + LOGO=