From: "Sergey Popov" <pinkbyte@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-firewall/ipt_netflow/
Date: Tue, 3 Oct 2017 08:15:50 +0000 (UTC) [thread overview]
Message-ID: <1507018540.3a2b5088d321100df65ea1946ace26faf35be07c.pinkbyte@gentoo> (raw)
commit: 3a2b5088d321100df65ea1946ace26faf35be07c
Author: Sergey Popov <pinkbyte <AT> gentoo <DOT> org>
AuthorDate: Tue Oct 3 08:15:16 2017 +0000
Commit: Sergey Popov <pinkbyte <AT> gentoo <DOT> org>
CommitDate: Tue Oct 3 08:15:40 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3a2b5088
net-firewall/ipt_netflow: fix incorrect handling of natevents configure option
Reported-by: Toralf Förster <toralf <AT> gentoo.org>
Closes: https://bugs.gentoo.org/632472
Package-Manager: Portage-2.3.10, Repoman-2.3.1
net-firewall/ipt_netflow/ipt_netflow-2.2-r2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-firewall/ipt_netflow/ipt_netflow-2.2-r2.ebuild b/net-firewall/ipt_netflow/ipt_netflow-2.2-r2.ebuild
index 9fa1da5e448..c2ed5f6f427 100644
--- a/net-firewall/ipt_netflow/ipt_netflow-2.2-r2.ebuild
+++ b/net-firewall/ipt_netflow/ipt_netflow-2.2-r2.ebuild
@@ -84,7 +84,7 @@ src_configure() {
--kdir="${KV_DIR}" \
--kver="${KV_FULL}" \
$(use debug && echo '--enable-debugfs') \
- $(use_enable natevents) \
+ $(use natevents && echo '--enable-natevents') \
$(use snmp && echo '--enable-snmp-rules' || echo '--disable-snmp-agent')
}
next reply other threads:[~2017-10-03 8:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 8:15 Sergey Popov [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-08 7:35 [gentoo-commits] repo/gentoo:master commit in: net-firewall/ipt_netflow/ Sergey Popov
2023-09-08 7:35 Sergey Popov
2023-06-27 9:12 Sergey Popov
2022-03-28 7:30 Sergey Popov
2021-03-10 1:24 Sam James
2020-12-02 7:19 Sergey Popov
2020-11-15 15:05 Sergey Popov
2020-11-15 15:05 Sergey Popov
2020-08-19 8:38 Jeroen Roovers
2020-08-12 6:47 Jeroen Roovers
2020-04-25 8:32 Jeroen Roovers
2019-12-29 13:21 Jeroen Roovers
2019-12-27 18:51 Jeroen Roovers
2019-12-27 18:51 Jeroen Roovers
2019-06-23 13:38 Jeroen Roovers
2019-06-23 13:38 Jeroen Roovers
2019-06-20 7:10 Jeroen Roovers
2019-06-19 5:35 Jeroen Roovers
2019-06-03 9:10 Jeroen Roovers
2019-02-25 19:19 Jeroen Roovers
2018-06-15 16:01 Sergey Popov
2018-03-20 13:52 Sergey Popov
2018-02-13 10:59 Jeroen Roovers
2017-10-16 8:56 Sergey Popov
2017-10-16 8:56 Sergey Popov
2017-09-29 14:51 Sergey Popov
2016-09-22 5:16 Sergey Popov
2016-09-22 5:16 Sergey Popov
2016-05-12 9:51 Sergey Popov
2016-05-12 9:51 Sergey Popov
2016-03-02 8:12 Sergey Popov
2016-03-02 7:56 Sergey Popov
2016-01-28 19:41 Sergey Popov
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=1507018540.3a2b5088d321100df65ea1946ace26faf35be07c.pinkbyte@gentoo \
--to=pinkbyte@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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