From: Santiago Vila <sanvila@unex.es>
To: sedat.dilek@gmail.com, 1008735@bugs.debian.org,
Gioele Barabucci <gioele@svario.it>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org
Subject: Re: Bug#1008735: base-files: /etc/os-release should contain VERSION variables for testing and unstable
Date: Mon, 3 Oct 2022 23:47:02 +0200 [thread overview]
Message-ID: <c5bf25ac-ff9c-bd7c-e998-c2fe8af3770e@unex.es> (raw)
In-Reply-To: <CA+icZUXQgnhcsjHMcm_KwD4O6FfUFv1vTDmdW4vGJ6oX-Y1GnA@mail.gmail.com>
El 3/10/22 a las 11:55, Sedat Dilek escribió:
> VERSION_ID=sid
> VERSION_CODENAME=bookworm
This is "schizophrenic", so to speak, and I don't think it is a good idea.
I've simply added VERSION_CODENAME=bookworm.
The only caveat is that testing and unstable are sides of the same coin,
but this is already explained in /usr/share/doc/base-files/FAQ.
As a result, if you take the VERSION_CODENAME string and include it in a
kernel version string somewhere, the meaning of such string is that the
kernel image was created in either a bookworm or a sid distribution.
I think this is good enough for most purposes. If you need more
fine-tuning, somebody should investigate what kind of magic lsb_release
did in the past and reenable part of it.
Thanks.
next prev parent reply other threads:[~2022-10-03 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164872694772.208797.12124885046362540124.reportbug@drop.zugschlus.de>
2022-10-03 9:55 ` base-files: /etc/os-release should contain VERSION variables for testing and unstable Sedat Dilek
2022-10-03 21:47 ` Santiago Vila [this message]
2022-10-13 14:02 ` Masahiro Yamada
2022-10-13 22:08 ` Sedat Dilek
2022-10-14 10:10 ` Gioele Barabucci
2022-10-14 19:58 ` Masahiro Yamada
2022-10-15 8:56 ` Sedat Dilek
2022-10-15 15:45 ` Gioele Barabucci
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c5bf25ac-ff9c-bd7c-e998-c2fe8af3770e@unex.es \
--to=sanvila@unex.es \
--cc=1008735@bugs.debian.org \
--cc=gioele@svario.it \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=sedat.dilek@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox