I had similar issues with a recent update that modified PRETTY_NAME in os-release. The format of the file is a list of environment-like shell-compatible variable assignments. The value of PRETTY_NAME after being modified was not double-quoted but included spaces which is not compatible with that format. This prevented certain packages from being configured properly during installation and temporarily broke an image I was working with:
PRETTY_NAME=TEST_20210106 customized using Cubic on {date}
until I fixed the value:
PRETTY_NAME="TEST_20210106 customized using Cubic on {date}"
The package was able to successfully install with a properly-formatted value.
I had similar issues with a recent update that modified PRETTY_NAME in os-release. The format of the file is a list of environment-like shell-compatible variable assignments. The value of PRETTY_NAME after being modified was not double-quoted but included spaces which is not compatible with that format. This prevented certain packages from being configured properly during installation and temporarily broke an image I was working with:
PRETTY_ NAME=TEST_ 20210106 customized using Cubic on {date}
until I fixed the value:
PRETTY_ NAME="TEST_ 20210106 customized using Cubic on {date}"
The package was able to successfully install with a properly-formatted value.