From: el-remph <el-remph@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] runit-void: load apparmor profiles from symlinks in /etc/apparmor.d
Date: Thu, 02 Jan 2025 17:49:23 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53812@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
There is a new pull request by el-remph against master on the void-packages repository
https://github.com/el-remph/void-packages apparmor-load-symlinks
https://github.com/void-linux/void-packages/pull/53812
runit-void: load apparmor profiles from symlinks in /etc/apparmor.d
#### Testing the changes
- I tested the changes in this PR: **YES**
Fixes: the existing script doesn't load apparmor profiles from symlinks, so eg. if you symlink to one of the /usr/share/apparmor/extra-profiles/, that will be silently skipped
This also doesn't rely on shell whitespace splitting (ot that there should be whitespace anywhere in these filenames anyway)
A patch file from https://github.com/void-linux/void-packages/pull/53812.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-apparmor-load-symlinks-53812.patch --]
[-- Type: text/x-diff, Size: 1493 bytes --]
From 790a4aece7b3f0f644dd966c940a875b1afc4ef7 Mon Sep 17 00:00:00 2001
From: remph <lhr@disroot.org>
Date: Tue, 24 Dec 2024 14:37:03 +0000
Subject: [PATCH] runit-void: load apparmor profiles from symlinks in
/etc/apparmor.d
---
srcpkgs/runit-void/files/09-apparmor.sh | 2 +-
srcpkgs/runit-void/template | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/runit-void/files/09-apparmor.sh b/srcpkgs/runit-void/files/09-apparmor.sh
index 1d24b4e349cd2b..e2c87a6b6225fd 100644
--- a/srcpkgs/runit-void/files/09-apparmor.sh
+++ b/srcpkgs/runit-void/files/09-apparmor.sh
@@ -18,7 +18,7 @@ if [ -n "$APPARMOR" ]; then
[ "$APPARMOR" = "complain" ] && AACOMPLAIN="-C"
if [ -d /etc/apparmor.d -a -x /usr/bin/apparmor_parser ]; then
- apparmor_parser -a $AACOMPLAIN $(find /etc/apparmor.d -maxdepth 1 -type f ! -name '*.new-*_*')
+ find -L /etc/apparmor.d -maxdepth 1 -type f ! -name '*.new-*_*' -exec apparmor_parser -a $AACOMPLAIN -- {} +
else
printf '! AppArmor installation problem - ensure you have installed apparmor package\n'
fi
diff --git a/srcpkgs/runit-void/template b/srcpkgs/runit-void/template
index dc74a41785cab0..a11b567d43e2c6 100644
--- a/srcpkgs/runit-void/template
+++ b/srcpkgs/runit-void/template
@@ -1,7 +1,7 @@
# Template file for 'runit-void'
pkgname=runit-void
version=20231124
-revision=5
+revision=6
build_style=gnu-makefile
short_desc="Void Linux runit scripts"
maintainer="Enno Boland <gottox@voidlinux.org>"
next reply other threads:[~2025-01-02 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 16:49 el-remph [this message]
2025-01-02 19:30 ` [PR REVIEW] " classabbyamp
2025-01-07 14:55 ` [PR PATCH] [Updated] " el-remph
2025-01-07 14:56 ` [PR REVIEW] " el-remph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53812@inbox.vuxu.org \
--to=el-remph@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).