5a0d3356ef
In FCOS we have a kola test that basically does `rpm -q python`. It's...a bit silly to spawn a whole VM for this. Ensuring that some specific packages don't get included has come up in a few cases. I think FCOS/RHCOS at least will want to blacklist `dnf` for example. And as noted above, FCOS could blacklist `python`. One major benefit of doing this inside rpm-ostree is that one gets the full "libsolv error message experience" when dependency resolution fails, e.g. blacklisting `glibc` I get: ``` Problem 79: conflicting requests - package coreos-installer-systemd-0.1.2-1.fc31.x86_64 requires coreos-installer = 0.1.2-1.fc31, but none of the providers can be installed - package coreos-installer-0.1.2-1.fc31.x86_64 requires rtld(GNU_HASH), but none of the providers can be installed - package glibc-2.30-10.fc31.x86_64 is filtered out by exclude filtering - package glibc-2.30-7.fc31.x86_64 is filtered out by exclude filtering - package glibc-2.30-8.fc31.x86_64 is filtered out by exclude filtering - package glibc-2.30-5.fc31.i686 is filtered out by exclude filtering - package glibc-2.30-5.fc31.x86_64 is filtered out by exclude filtering - package glibc-2.30-10.fc31.i686 is filtered out by exclude filtering ``` |
||
---|---|---|
.. | ||
libbasic-test.sh | ||
libcomposetest.sh | ||
runtest.sh | ||
test-basic-unified.sh | ||
test-basic.sh | ||
test-boot-location-modules.sh | ||
test-boot-location-new.sh | ||
test-excludes.sh | ||
test-install-langs.sh | ||
test-installroot.sh | ||
test-lockfile.sh | ||
test-machineid-compat.sh | ||
test-misc-tweaks.sh | ||
test-mutate-os-release.sh | ||
test-rojig-e2e.sh | ||
test-rojig-pure.sh | ||
test-write-commitid.sh |