From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: apparmor: move rules to a separate package
Date: Mon, 17 May 2021 12:07:57 +0200 [thread overview]
Message-ID: <20210517100757.nfDCMaceDRy1Sf59Ktz1wLECwi13A0M4YoLrI7-tSpI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30946@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/30946#issuecomment-842197023
Comment:
Before this PR, the apparmor package provided all rules on its own - void specific and upstream roles. This resulted in broken rules when packages were updated, so I created a package which tracks apparmor master (apparmor-rules-upstream) and a meta package which provides void specific rules (apparmor-rules-void). The rules have an ABI version specified inside, so there shouldn't be any problems with apparmor being older than the rules.
This update will probably create a lot of .new files in /etc/apparmor.d/local/ for users, but it shouldn't matter.
The upstream rule package has an update file which shows a new version when there are new commits in the profiles/ directory in the apparmor repository.
next prev parent reply other threads:[~2021-05-17 10:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 9:41 [PR PATCH] " paper42
2021-05-17 9:58 ` [PR PATCH] [Updated] " paper42
2021-05-17 10:06 ` paper42
2021-05-17 10:07 ` paper42 [this message]
2021-05-17 12:30 ` Duncaen
2021-05-17 12:32 ` [PR REVIEW] " Duncaen
2021-05-17 12:43 ` ericonr
2021-05-17 13:24 ` [PR REVIEW] " paper42
2021-05-17 13:47 ` paper42
2021-05-17 13:55 ` noarchwastaken
2021-05-17 13:57 ` [PR PATCH] [Updated] " paper42
2021-05-17 14:04 ` noarchwastaken
2021-05-17 14:04 ` noarchwastaken
2021-05-17 14:04 ` noarchwastaken
2021-05-23 19:01 ` noarchwastaken
2021-05-23 19:05 ` noarchwastaken
2021-07-05 21:09 ` [PR PATCH] [Closed]: " paper42
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=20210517100757.nfDCMaceDRy1Sf59Ktz1wLECwi13A0M4YoLrI7-tSpI@z \
--to=paper42@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).