Dear Masahiro, dear Sedat,
[Debian bug #1008735 removed from CC]
On 13/10/22 16:02, Masahiro Yamada wrote:
On Mon, Oct 3, 2022 at 6:56 PM Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote:
Can you give me more context of this email?
I am using Debian/unstable AMD64 and doing Linux-kernel upstream
development and testing.
People using bindeb-pkg (mkdebian) from Linux-kernel sources
(scripts/packages) to build and test their selfmade Debian kernels get
a now a "n/a" for distribution.
Right, if I try the latest sid,
"lsb_release -cs" returns "n/a".
It returned "sid" before IIRC.
What was changed in Debian?
Any change in the lsb_release program?
A quick summary from the upstream developer (me) of the new
`lsb_release` implementation being rolled out in Debian.
Debian dropped the legacy `lsb_release` package. Now the `lsb_release`
command is provided by `lsb-release-minimal`.
`lsb-release-minimal` relies on `/etc/os-release` to provide LSB
information in a format that is byte-for-byte compatible with the
`lsb_release` specifications.
The issue you experienced is due to Debian's `/etc/os-release` (provided
by the `base-files` package) not contain all the necessary information.
See <https://bugs.debian.org/1008735>.
The situation is now changing. The maintainer of `base-files` has added
VERSION_CODENAME ("bookworm" for both unstable and testing).
However VERSION_ID (used for `lsb_release --release`) has not been added
yet. This is being tracked at <https://bugs.debian.org/1021663>.
Until #1021663 is fixed, `lsb_release -rc` will return the following
info in both unstable and testing.
Release: n/a
Codename: bookworm
A workaround to get the old behavior is:
rm /etc/os-release
cp /usr/lib/os-release /etc/os-release
echo "VERSION_ID=unstable" >> /etc/os-release
echo "VERSION_CODENAME=sid" >> /etc/os-release
Regards,
--
Gioele Barabucci
