chore: drop btrfs support from expand-on-first-boot
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · Felix Moessbauer via lists.cip- project.org
We currently add a dependency to btrfs-progs via the expand-on-first-boot package, despite we don't have a single target in cip that uses btrfs. As we can't make that assumption for downstream users, we only drop that dependency for the internal targets (via the kas include).
Any news on this? Did it slip through?
Felix
Quoted 22 lines
Signed-off-by Felix Moessbauer <[email protected]>---
Note: This has been found while working on the CIS hardening.kas/opt/expand-on-first-boot.yml | 1 + 1 file changed, 1 insertion(+)kas/opt/expand-on-first-boot.yml +1
-0@@ -15,6 +15,7 @@ header: local_conf_header: package-expand-on-first-boot: | IMAGE_INSTALL:append = " expand-on-first-boot" + EXPAND_FSTYPES:remove = "btrfs" expand-before-encrypt: | IMAGE_INSTALL:remove:encrypt-partitions = "expand-on-first-boot" CRYPT_PARTITIONS:append:encrypt-partitions = ":expand"Signature · 1 line
2.53.0