On 06/08/26 22:31, Marc Haber wrote:
Is it the intended behavior that an unstable system managed with ansible
will report a DIFFERENT distribution_major_version depending on whether
lsb-release is installed or not?
Without lsb-release, VERSION_ID is "forky/sid", with lsb-release, it's
"n/a". Guess which variant makes more sense to me.
That is a different, but connected issue.
As you said, Debian still requires ad-hoc handling and there is no
consensus how that handling should happen. If you check `_distro.py` in
Ansible you'll see a series of Debian-specific code branches, some of
which will be executed only when `/usr/bin/lsb_release` is not
available. (For all other modern distros the data is gathered by simply
reading `{/etc,/usr/lib}/os-release`.)
Regards,
--
Gioele Barabucci
