Comment 3 for bug 2038664

The lsb-release package is available on Bookworm, and will be installed by default (even on a fresh install) in some scenarios, including where the Debian installer (using hw-detect) identifies your install as running on a VMware hypervisor, and installs open-vm-tools (which pulls in the lsb-release package by requiring it).

While the lsb_release command outputs the "No LSB modules are available." message in more places as of Bookworm, it only outputs the message if stdout is a terminal, thus our usage appears to be unaffected.

I think that Josh's suggestion of ensuring that the lsb-release package is installed is very reasonable.

If we need to switch/simplify, I think Galen's on the right path with using the os-release file.

/usr/lib/os-release and the symlink /etc/os-release are provided by base-files, and are present in all Debian releases that we currently support.

our two uses of lsb_release are:

Open-ILS/src/edi_translator/install-ubuntu.sh:UBUNTU_RELEASE=$(lsb_release -sc)
Open-ILS/src/extras/install/Makefile.debian:RELEASE_CODENAME=$(shell lsb_release -cs)

It may be as simple as changing "lsb_release -sc" and "lsb_release -cs" to ". /usr/lib/os-release; echo $VERSION_CODENAME"?

(I haven't tested that within the Makefile environment)