From 771c87e8cd9f59e029aec2bf2fd7e666e0554816 Mon Sep 17 00:00:00 2001
From: renner <80410025+renner0e@users.noreply.github.com>
Date: Sun, 11 Oct 2026 15:28:06 +0000
Subject: [PATCH] feat: remove v4l2loopback from initramfs (#3002)

This makes the initramfs reproducible, because currently the
kmod-v4l2loopback is the only thing that is not reproducible.

This is not the proper way to do this, it has to be fixed in
ublue-os/akmods and see what step introduces timestamps into the build.

xref: https://github.com/ublue-os/aurora/issues/2579
---
 build_scripts/base/19-initramfs.sh | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/build_scripts/base/19-initramfs.sh b/build_scripts/base/19-initramfs.sh
index ac287734..fa105ab2 100755
--- a/build_scripts/base/19-initramfs.sh
+++ b/build_scripts/base/19-initramfs.sh
@@ -7,6 +7,14 @@ set -ouex pipefail
 KERNEL_VERSION=$(rpm -q --queryformat="%{evr}.%{arch}" kernel-core)
 INITRAMFS="/usr/lib/modules/${KERNEL_VERSION}/initramfs.img"
 
+V4L2_PATH="$(rpm -ql kmod-v4l2loopback)"
+
+DRACUT_REMOVE=(
+  # makes no difference if in initramfs or not
+  # this is a hack FIXME in ublue-os/akmods
+  ${V4L2_PATH} # ko.kz file has build id's changing -> non-reproducible
+)
+
 # https://github.com/ublue-os/aurora/issues/2568
 # these strings change with every build
 TMP_OS_RELEASE=$(mktemp --tmpdir 'os-release-XXXXXXXXXX')
@@ -19,6 +27,7 @@ DRACUT_NO_XATTR=1 /usr/bin/dracut \
   --reproducible \
   --verbose \
   --force \
+  --remove "${DRACUT_REMOVE[@]}" \
   "${INITRAMFS}"
 
 # mv causes permissions to change