From b0daed85e7787ec6c7fe640cf151af26a318151e Mon Sep 17 00:00:00 2001 From: Thomas Perale Date: Sat, 9 Aug 2025 19:54:17 +0200 Subject: [PATCH] package/libapparmor: remove stale reference to patch 0001 The AUTORECONF variable was introduced in commit [1] with reference to the patches that modified the m4 and Makefile.am files. The commit [2] removed the last such patch but left the reference to the patch and the AUTORECONF variable. Later, commit [3] updated the mirror to the gitlab URL that no longer bundle a pre-generated `configure` file, making the execution of AUTORECONF necessary anyway. This patch removes the obsolete reference to the patch 0001 removed in [2] to avoid ambiguity with the new patch 0001 introduced in commit [4]. [1] 01a82c1401 package/libapparmor: enable python bindings [2] 27cd0b5033 package/apparmor: bump to version 3.0.4 [3] 5649202ddc package/libapparmor: bump to version 3.1.7 [4] 2640f5dcd0 package/libapparmor: fix build w/ musl Signed-off-by: Thomas Perale [Peter: add a comment explaining why] Signed-off-by: Peter Korsgaard (cherry picked from commit 50cac72f73f7eee9136aa9cc48dbd5a5a12a0625) Signed-off-by: Thomas Perale --- package/libapparmor/libapparmor.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/libapparmor/libapparmor.mk b/package/libapparmor/libapparmor.mk index fa59ff2924..91c22ad35b 100644 --- a/package/libapparmor/libapparmor.mk +++ b/package/libapparmor/libapparmor.mk @@ -16,7 +16,7 @@ LIBAPPARMOR_DEPENDENCIES = host-bison host-flex host-pkgconf LIBAPPARMOR_SUBDIR = libraries/libapparmor LIBAPPARMOR_INSTALL_STAGING = YES -# Patch 0001 touches Makefile.am and m4 files +# no configure in tarball LIBAPPARMOR_AUTORECONF = YES # Most AppArmor tools will want to link to the static lib.