From: Patrick McHardy <kaber@trash.net>
To: Kevin Fenzi <kevin@scrye.com>
Cc: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>,
netfilter-devel@vger.kernel.org
Subject: Re: nftables/libnftables packages for Fedora
Date: Mon, 13 Jan 2014 00:18:26 +0000 [thread overview]
Message-ID: <20140113001826.GC3251@macbook.localnet> (raw)
In-Reply-To: <20140112170549.327dd807@voldemort.scrye.com>
On Sun, Jan 12, 2014 at 05:05:49PM -0700, Kevin Fenzi wrote:
> [ re-sending as I forgot to cc the list ]
>
> On Sun, 12 Jan 2014 22:16:35 +0100
> Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com> wrote:
>
> ...snip...
>
> > There is a patch from me to address this:
> > http://patchwork.ozlabs.org/patch/304866/
> > Feel free to test it and comment.
> >
> > I have the same issue in the Debian land. I applied the patch locally
> > in the package as a workaround.
> >
> > The patch is not applied yet to upstream.
>
> Cool.
>
> That addresses the part of the issue where the interpreter isn't fully
> specified, but still the question is if these are config files that
> users are expected to modify or are noarch scripts provided by the
> package that are expected to be read-only (ie, /etc vs /usr/share)?
Yes, they are basically noarch scripts providing defaults for the
table configurations.
next prev parent reply other threads:[~2014-01-13 0:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 20:40 nftables/libnftables packages for Fedora Kevin Fenzi
2014-01-12 21:16 ` Arturo Borrero Gonzalez
2014-01-13 0:05 ` Kevin Fenzi
2014-01-13 0:18 ` Patrick McHardy [this message]
2014-01-13 0:11 ` Kevin Fenzi
2014-01-15 9:53 ` Pablo Neira Ayuso
2014-01-15 10:18 ` Arturo Borrero Gonzalez
2014-01-13 0:25 ` Patrick McHardy
2014-01-13 0:17 ` Patrick McHardy
2014-01-13 0:29 ` Patrick McHardy
2014-01-13 8:54 ` Jan Engelhardt
2014-01-13 9:09 ` Patrick McHardy
2014-01-13 19:18 ` Kevin Fenzi
2014-01-14 8:55 ` Patrick McHardy
2014-01-14 18:28 ` Kevin Fenzi
2014-01-14 18:34 ` Pablo Neira Ayuso
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=20140113001826.GC3251@macbook.localnet \
--to=kaber@trash.net \
--cc=arturo.borrero.glez@gmail.com \
--cc=kevin@scrye.com \
--cc=netfilter-devel@vger.kernel.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).