Source: audit Followup-For: Bug #1148286 Hello,
Well I'm not planning to keep a patch forever in the debian package, while from my understanding the issue is in apparmor/kernel. I still didn't get an answer on why apparmor cannot change the event ID to the one that were assigned to them. This is something that is known for years (10y+) and nothing was done on the apparmor side. So this, for me, is a WONTFIX again. Kind regards, Laurent Bigonville -- System Information: Debian Release: forky/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 7.1.13+deb14-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
