From: Kevin Fenzi <kevin@scrye.com>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nftables/libnftables packages for Fedora
Date: Sun, 12 Jan 2014 17:05:49 -0700 [thread overview]
Message-ID: <20140112170549.327dd807@voldemort.scrye.com> (raw)
In-Reply-To: <CAOkSjBhCTDCDzBLp86d1qA+xH=KMZtz2HrU3QfnZ+8AJ+qcWTg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]
[ 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)?
> > 6. I recently enabled the xml stuff in libnftables and am seeing a
> > number of tests fail:
> >
> > parsing xmlfiles/55-rule-real.xml: [31mFAILED [0m (Invalid
> > argument) and
> > parsing xmlfiles/74-set.xml: [31mFAILED [0m (Invalid argument)
> > mxml: <!-- nft add rule filter output ct secmark 0 counter -->
> > cannot be a second root node after <nftables>
> >
>
> I can't see the libmxml version in the build log. Which version of
> libmxml are you using?
> Seem that your version of libmxml treats XML comments different than
> in my version (libmxml 2.6 from Debian).
2.7 here. ;) So, likely that changed between 2.6 and 2.7?
> Also I guess you are using an outdated snapshot of libnftables. Some
> important changes happened to the XML/JSON parsers.
Hum, thats the 2014-01-11 snapshot. Not very old.
> Anyway, thanks for the report, I'm going to review the XML parser.
Thank you.
> > Are these expected? The Invalid argument might be because it doesn't
> > have nftables available in the build kernel? But the json tests
> > work. :(
> >
>
> Not expected at all.
>
> These tests simply parse the XML/JSON input, they don't send anything
> to the kernel.
ok. Great
> > Thanks. Again, if I should send this somewhere else instead, just
> > let me know. Comments welcome here, direct email and/or in the
> > above review bugs. ;)
>
>
> I think this is the right place.
Excellent. Thanks.
kevin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-13 0:11 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 [this message]
2014-01-13 0:18 ` Patrick McHardy
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=20140112170549.327dd807@voldemort.scrye.com \
--to=kevin@scrye.com \
--cc=arturo.borrero.glez@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.