From: the-antz <the-antz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] apparmor: fix dhcpcd profile
Date: Sat, 14 Mar 2020 17:33:50 +0100 [thread overview]
Message-ID: <20200314163350.4UH7ANySgUB5f7_Q3WlYR74hKdP_O1DWF9T9uUzz9os@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20080@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
New comment by the-antz on void-packages repository
https://github.com/void-linux/void-packages/pull/20080#issuecomment-599092927
Comment:
Somehow building/installing the package locally results in "Invalid capability net_bind_service" when trying to load most (unchanged) profiles.
Is there something special with this package that needs to be cared about? The changed profile itself works fine for me but installing it as new rev-bumped package breaks it somehow.
next parent reply other threads:[~2020-03-14 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20080@inbox.vuxu.org>
2020-03-14 16:33 ` the-antz [this message]
2020-03-14 16:47 ` the-antz
2020-03-14 16:59 ` the-antz
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=20200314163350.4UH7ANySgUB5f7_Q3WlYR74hKdP_O1DWF9T9uUzz9os@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).