fix: the login message welcomes to Keel Linux, with the hostname as it is #1

Merged

marcos-mendez merged 1 commit from fix/motd-keel-linux-welcome into keel/trixie

2026-10-03 01:15:44 -03:00

marcos-mendez commented

2026-10-02 22:49:28 -03:00

(Migrated from github.com)

On a live Keel Web container (2026-10-03) the motd read "Welcome to Keel-web1, TurnKey GNU/Linux 19.0 (Debian 13/Trixie)". It now reads "Welcome to keel-web1, Keel Linux 19.0 (Debian 13/Trixie)".

contrib/motd took the line from sysversion.fmt_sysversion (turnkey-version), whose TurnKey wording the fork deliberately keeps. The line is composed here instead, in libsysinfo/welcome.py: release from /etc/keel_version, falling back to /etc/turnkey_version (common, decision 0014), base distribution from lsb_release as before, upstream's fallbacks when one or both are missing.
Hostname printed as the machine has it. Upstream's str.capitalize() uppercased the first letter and lowercased the rest ("Keel-web1"), which the brief says to drop.
debian/control Description and pyproject.toml summary say Keel Linux. Copyright headers, package/command names and the upstream Homepage are kept. The TKLBAM block of turnkey-sysinfo is untouched: common's motd drop-in already cuts it, and whether an appliance ships TKLBAM is handbook#6.
tests/test_welcome.py, 21 pytest cases, run by pybuild during dpkg-buildpackage (python3-pytest added to Build-Depends), so the existing "build / trixie" check runs them; no new workflow. Verified locally: the build runs the suite and produces turnkey-sysinfo_1.1.0+keel2_all.deb with libsysinfo/welcome.py and contrib/motd.
1.1.0+keel2 with a changelog entry.

Note: the turnkey-version fork has no tests in its tree, so there was no fork test layout to copy; pytest under pybuild is the Debian-native way for a pyproject package and needs no runner change.

On a live Keel Web container (2026-10-03) the motd read "Welcome to Keel-web1, TurnKey GNU/Linux 19.0 (Debian 13/Trixie)". It now reads "Welcome to keel-web1, Keel Linux 19.0 (Debian 13/Trixie)". - `contrib/motd` took the line from `sysversion.fmt_sysversion` (turnkey-version), whose TurnKey wording the fork deliberately keeps. The line is composed here instead, in `libsysinfo/welcome.py`: release from `/etc/keel_version`, falling back to `/etc/turnkey_version` (common, decision 0014), base distribution from lsb_release as before, upstream's fallbacks when one or both are missing. - Hostname printed as the machine has it. Upstream's `str.capitalize()` uppercased the first letter and lowercased the rest ("Keel-web1"), which the brief says to drop. - `debian/control` Description and `pyproject.toml` summary say Keel Linux. Copyright headers, package/command names and the upstream Homepage are kept. The TKLBAM block of `turnkey-sysinfo` is untouched: common's motd drop-in already cuts it, and whether an appliance ships TKLBAM is handbook#6. - `tests/test_welcome.py`, 21 pytest cases, run by pybuild during `dpkg-buildpackage` (`python3-pytest` added to Build-Depends), so the existing "build / trixie" check runs them; no new workflow. Verified locally: the build runs the suite and produces `turnkey-sysinfo_1.1.0+keel2_all.deb` with `libsysinfo/welcome.py` and `contrib/motd`. - 1.1.0+keel2 with a changelog entry. Note: the turnkey-version fork has no tests in its tree, so there was no fork test layout to copy; pytest under pybuild is the Debian-native way for a pyproject package and needs no runner change.