From: noarchwastaken <noarchwastaken@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: apparmor: move rules to a separate package
Date: Mon, 17 May 2021 16:04:09 +0200 [thread overview]
Message-ID: <20210517140409.8qIhg6u_nazn9niHrjRlOqgQxvoJ4Evp_3bmeZE2-RE@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: 4205 bytes --]
New comment by noarchwastaken on void-packages repository
https://github.com/void-linux/void-packages/pull/30946#issuecomment-842352140
Comment:
> @noarchwastaken <https://github.com/noarchwastaken>, I noticed the patch you added for dnsmasq is not in the master branch of apparmor, would you like to make a PR there? TBH, I'm not sure if it's a Void-specific issue. I have other machines running Arch and Fedora 33 and they work fine. I guess I have to dig into the package for those distros... If it is an upstream issue, sure I will make a PR there.
> […](#)
> On 5/17/21 5:41 AM, paper wrote: General * This is a new package and it conforms to the quality requirements <https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements> Have the results of the proposed changes been tested? * I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me * I generally don't use the affected packages but briefly tested this PR @noarchwastaken <https://github.com/noarchwastaken>, I noticed the patch you added for dnsmasq is not in the master branch of apparmor, would you like to make a PR there? ------------------------------------------------------------------------ You can view, comment on, or merge this pull request online at: #30946 <#30946> Commit Summary * New package: apparmor-rules-upstream-2021.04.21 * New package: apparmor-rules-void-2021.05.17 * apparmor: move rules to a separate package File Changes * *A* srcpkgs/apparmor-rules-upstream/template <https://github.com/void-linux/void-packages/pull/30946/files#diff-1b14944e695a352b43329d96ebf0096e9e0f8757a36247af92f551125d329512> (35) * *A* srcpkgs/apparmor-rules-upstream/update <https://github.com/void-linux/void-packages/pull/30946/files#diff-256d89f085b5f71e7c7e8f4a085305499f6c827ef780795c5d9425f3fba4613a> (2) * *R* srcpkgs/apparmor-rules-void/files/profiles/usr.bin.dhcpcd <https://github.com/void-linux/void-packages/pull/30946/files#diff-a3eaf6944249ee5cf3f40693391859459eb6439cbfc1223ce343bb1052a16467> (0) * *R* srcpkgs/apparmor-rules-void/files/profiles/usr.bin.nginx <https://github.com/void-linux/void-packages/pull/30946/files#diff-60fe4867b37b8a5da8967b89e381d1c812e6502a9ba0e901b0773094a62689e1> (0) * *R* srcpkgs/apparmor-rules-void/files/profiles/usr.bin.php-fpm <https://github.com/void-linux/void-packages/pull/30946/files#diff-615eb875378401831e96bd99db3bd0704fa5eb1ac6dc42ebc4ce94d015516bf5> (0) * *R* srcpkgs/apparmor-rules-void/files/profiles/usr.bin.pulseaudio <https://github.com/void-linux/void-packages/pull/30946/files#diff-bc51334447bea3cfbc105b321f21be0600463fea83cbea8ff6a46aee3b7892e2> (0) * *R* srcpkgs/apparmor-rules-void/files/profiles/usr.bin.uuidd <https://github.com/void-linux/void-packages/pull/30946/files#diff-f1513c7cd3248f108d00cc4e53e34d3d742fa811139b162618281f81c33dd746> (0) * *R* srcpkgs/apparmor-rules-void/files/profiles/usr.bin.wpa_supplicant <https://github.com/void-linux/void-packages/pull/30946/files#diff-f630e66a19e9592b2fbfcfdb2be3212b5bc184593a796b8e82d928f669f3437c> (0) * *A* srcpkgs/apparmor-rules-void/template <https://github.com/void-linux/void-packages/pull/30946/files#diff-ccb01036edac1cf785aea1df7bba251afd3097b4524fe95225198fefd703323e> (15) * *D* srcpkgs/apparmor/patches/fix-dnsmasq-libvirt.patch <https://github.com/void-linux/void-packages/pull/30946/files#diff-9c8d2ca3ae818491b9f89ef1d147d2561951e1b0c889b33a751da241f83b32c2> (13) * *M* srcpkgs/apparmor/template <https://github.com/void-linux/void-packages/pull/30946/files#diff-95b5046d4411626948f0992cfa17ed0317b6397217d7916dd1d4fa86ad1de2e2> (27) Patch Links: * https://github.com/void-linux/void-packages/pull/30946.patch <https://github.com/void-linux/void-packages/pull/30946.patch> * https://github.com/void-linux/void-packages/pull/30946.diff <https://github.com/void-linux/void-packages/pull/30946.diff> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#30946>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARLIKXJ4MUJ4KQGSWN5ABDTTODQFTANCNFSM45AC77HQ>.
Ah wait, FC33 is using SELinux. For Arch, I have to check the apparmor status on that...
next prev parent reply other threads:[~2021-05-17 14:04 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
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 [this message]
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=20210517140409.8qIhg6u_nazn9niHrjRlOqgQxvoJ4Evp_3bmeZE2-RE@z \
--to=noarchwastaken@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).