On Mon, Oct 03, 2022 at 08:04:22AM +0200, Gioele Barabucci wrote: > A workaround (while waiting for the root issue #1008735 to be fixed) is to > add to `/etc/os-release` the following two lines: > > ``` > VERSION_ID=unstable > VERSION_CODENAME=bookwork > ```
This will be in my ansible playbooks in the future. It will probably also mean that I need to manage /etc/os-release even on stable systems with ansible as well to cater for systems that got installed as unstable/testing and then went stable with the release. BUt at least this saves me from patching gazillions of rules and getting snappy answers from role autors why Debian is the only distribution that needs ugly (and ever changing!) workarounds in version gates. 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. Greetings Marc
