From: Robby Workman <rw@rlworkman.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Jan Engelhardt <jengelh@medozas.de>,
netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [ANNOUNCE] conntrack-tools 0.9.11 released
Date: Tue, 24 Feb 2009 08:10:42 -0600 [thread overview]
Message-ID: <20090224081042.0f37580e@liberty.rlwhome.lan> (raw)
In-Reply-To: <49A3C3FE.2000403@netfilter.org>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
On Tue, 24 Feb 2009 10:55:10 +0100
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> Robby Workman wrote:
> >
> > Weird that it's not affecting Jan then, because it's definitely
> > something specific to newer glibc (or perhaps gcc, but it's not
> > immediately obvious how that would be the case). I'm on Slackware
> > rather than Gentoo, running quite a bit of prerelease development
> > builds (including gcc-4.3.3 and glibc-2.9 along with 2.6.28.7
> > kernel).
>
> I'm don't mind too much as long as the following patch (which is
> already in git to fix the gentoo's problem) fixes also yours:
>
> http://git.netfilter.org/cgi-bin/gitweb.cgi?p=conntrack-tools.git;a=commitdiff;h=9bf002ff7935e7dff625683787fc3a06ac2ef2cb;hp=87c8c090e1b64eac27edb968845cb1e8ee65b06b
>
> Please, confirm that the problem is resolved.
Yes, that's exactly what I did locally to fix it -- confirmed.
-RW
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-02-24 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 17:40 [ANNOUNCE] conntrack-tools 0.9.11 released Pablo Neira Ayuso
2009-02-23 5:34 ` Robby Workman
2009-02-23 7:17 ` Jan Engelhardt
2009-02-23 9:19 ` Pablo Neira Ayuso
2009-02-23 15:34 ` Robby Workman
2009-02-23 16:55 ` Jan Engelhardt
2009-02-24 3:02 ` Robby Workman
2009-02-24 9:59 ` Jan Engelhardt
2009-02-24 9:55 ` Pablo Neira Ayuso
2009-02-24 14:10 ` Robby Workman [this message]
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=20090224081042.0f37580e@liberty.rlwhome.lan \
--to=rw@rlworkman.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.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