On Fri, Oct 14, 2022 at 12:10 PM Gioele Barabucci <gioele@xxxxxxxxx> wrote: > > 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 > Thanks for your clarifications and information. Adding your workaround (with which I agree and looks sane to me): I still see some issues: # lsb_release --all 2>/dev/null Distributor ID: Debian Description: Debian GNU/Linux bookworm/sid Release: unstable Codename: sid # lsb_release --codename --short 2>/dev/null sid I bet we need to change PRETTY_NAME as well and... # cat /etc/os-release PRETTY_NAME="Debian GNU/Linux bookworm/sid" NAME="Debian GNU/Linux" ID=debian VERSION_ID=unstable VERSION_CODENAME=sid HOME_URL="https://www.debian.org/"; SUPPORT_URL="https://www.debian.org/support"; BUG_REPORT_URL="https://bugs.debian.org/"; ( For Debian/testing "testing" and "bookworm" sounds reasonable to me (see Debian Bug #1021663). ) ( Guess Debian/stable then should contain "stable" and "buster"? ) ...who cares about? # cat /etc/debian_version bookworm/sid I am a long user of Debian/unstable AMD64 and I was seeing on boot, background of graphical login-manager and/or any info-tool like KDE/kinfocenter etc. Debian GNU/Linux $codename_of_current_testing/sid (current: bookworm/sid) When you want to change all that "old behaviour" then do it for all releases available on Debian, please. -Sedat-
