Github messages for voidlinux
 help / color / mirror / Atom feed
From: the-antz <the-antz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: apparmor: fix dhcpcd profile for dhcpcd version 9
Date: Thu, 09 Apr 2020 20:37:51 +0200	[thread overview]
Message-ID: <20200409183751.LVYLGx_PNDr6v_O2T2CvipWI7OhjTpSffBh3_uGgzX8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20752@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 611 bytes --]

New comment by the-antz on void-packages repository

https://github.com/void-linux/void-packages/pull/20752#issuecomment-611688356

Comment:
> It worked.
> 
> Though curiously the apparmor_parser commands were required even after a reboot (apparmor was not set to enforce due to the bug before reboot) i guess it loads the profiles from elsewhere than the directory and they need to be compiled?

Did you maybe enable the profile caching (it's off by default)? That'd do that. The cache gets updated when you load a profile manually.
Otherwise, no idea why it would not pick it up automatically on reboot.

  parent reply	other threads:[~2020-04-09 18:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 10:49 [PR PATCH] " the-antz
2020-04-08 11:29 ` [PR PATCH] [Updated] [NOMERGE] " the-antz
2020-04-09  2:22 ` LamaRaz
2020-04-09 14:54 ` the-antz
2020-04-09 15:37 ` LamaRaz
2020-04-09 17:59 ` the-antz
2020-04-09 18:26 ` LamaRaz
2020-04-09 18:37 ` the-antz [this message]
2020-04-11 15:44 ` [PR PATCH] [Updated] " the-antz
2020-04-11 15:44 ` the-antz
2020-04-11 16:58 ` CameronNemo
2020-04-13 17:27 ` CameronNemo
2020-04-13 17:32 ` [PR PATCH] [Merged]: " xtraeme

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=20200409183751.LVYLGx_PNDr6v_O2T2CvipWI7OhjTpSffBh3_uGgzX8@z \
    --to=the-antz@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).