On 14/08/25 00:33, NoisyCoil wrote:
I'll try and see if I can work around it for future installations to
minimize the number of affected users, before it gets fixed in
live-build.
The issue is fixed (or rather, worked around) in new installations.
Old trixie installations will not be affected in a meaningful way
before 2027 (they will still declare themselves to be version 13.0
instead of 13.x after the first trixie point release, but this is no
big deal), so I'll wait and see what fix is proposed by live-build.
As for old testing installations, testing becomes forky effective
today with an update of base-files to version 14 [1,2], so they are
already affected. To fix this issue manually in testing, one can
execute
```
sudo dpkg-divert --local --remove --no-rename --divert
/etc/os-release.debootstrap /etc/os-release
sudo apt-get install -y --reinstall base-files
```
I hope the fix for trixie, when implemented, will propagate to testing
too, so this is unnecessary. Again, let's see what happens.
Cheers!
[1]
https://tracker.debian.org/news/1653113/accepted-base-files-14-source-into-unstable/
[2]
https://tracker.debian.org/news/1655190/base-files-14-migrated-to-testing/