e94f8c9b5f
I noticed that the latest Fedora Atomic Host 28 and Silverblue did not have an `OSTREE_VERSION` line in `/etc/os-release` even though both specified `mutate-os-release` in their manifests. This turned out to be due to the fact that `/usr/lib/os-release` is now a symlink to a variant-specific file (e.g. `os-release-atomichost`), so we would fallback to mutating `/usr/lib/os.release.d/os-release-fedora` instead. Fix this by just taking the nuclear option of running `realpath` in the rootfs directly. This is more maintainable than trying to keep up with changes in variants/naming/etc. There's related discussions to this in the original [PR](https://github.com/projectatomic/rpm-ostree/pull/410) which introduced the feature re. resolving symlinks within the rootfs. Closes: #1481 Approved by: jlebon |
||
|---|---|---|
| .. | ||
| libbasic-test.sh | ||
| libcomposetest.sh | ||
| run-test.sh | ||
| test-basic-unified.sh | ||
| test-basic.sh | ||
| test-boot-location-new.sh | ||
| test-compose2jigdo.sh | ||
| test-install-langs.sh | ||
| test-installroot.sh | ||
| test-misc-tweaks.sh | ||
| test-mutate-os-release.sh | ||
| test-rojig-e2e.sh | ||
| test-write-commitid.sh | ||