From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nfdump/
Date: Thu, 23 Jun 2022 05:58:20 +0000 (UTC) [thread overview]
Message-ID: <1655963897.0967d9a460ca48e183bfb799bbd741c23e6a9d97.ago@gentoo> (raw)
commit: 0967d9a460ca48e183bfb799bbd741c23e6a9d97
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 23 05:58:17 2022 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Thu Jun 23 05:58:17 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0967d9a4
net-analyzer/nfdump: amd64 stable wrt bug #853832
Package-Manager: Portage-3.0.30, Repoman-3.0.3
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
net-analyzer/nfdump/nfdump-1.6.24.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-analyzer/nfdump/nfdump-1.6.24.ebuild b/net-analyzer/nfdump/nfdump-1.6.24.ebuild
index db24ffe43a66..3d187e837d08 100644
--- a/net-analyzer/nfdump/nfdump-1.6.24.ebuild
+++ b/net-analyzer/nfdump/nfdump-1.6.24.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/phaag/nfdump/archive/v${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="BSD"
SLOT="0/${PV}"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
IUSE="debug doc jnat ftconv nfpcapd nfprofile nftrack nsel readpcap sflow"
REQUIRED_USE="?? ( jnat nsel )"
next reply other threads:[~2022-06-23 5:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 5:58 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 22:06 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nfdump/ Sam James
2023-06-01 5:23 Sam James
2023-05-01 13:19 Sam James
2023-04-23 17:57 Sam James
2022-10-31 16:41 Agostino Sarubbo
2022-10-01 0:34 Sam James
2022-06-23 6:45 Agostino Sarubbo
2022-06-23 4:47 Sam James
2022-04-13 1:48 Sam James
2022-03-24 23:58 Sam James
2021-08-11 0:02 Sam James
2021-05-28 2:27 Sam James
2021-05-28 1:22 Sam James
2021-04-18 21:27 Sam James
2021-04-18 21:20 Sam James
2021-03-27 16:11 Sam James
2021-03-27 16:07 Sam James
2021-03-27 16:06 Sam James
2021-03-27 16:02 Sam James
2021-03-27 15:35 Sam James
2021-03-15 21:12 Sam James
2021-03-15 21:12 Sam James
2021-03-15 21:09 Sam James
2021-03-15 21:01 Sam James
2020-08-02 10:43 Jeroen Roovers
2020-03-29 12:38 Jeroen Roovers
2020-03-12 16:26 Agostino Sarubbo
2020-03-12 16:21 Agostino Sarubbo
2017-05-29 8:30 Jeroen Roovers
2016-06-15 9:13 Jeroen Roovers
2016-05-14 22:23 Agostino Sarubbo
2016-05-14 22:22 Agostino Sarubbo
2016-05-12 16:39 Jeroen Roovers
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=1655963897.0967d9a460ca48e183bfb799bbd741c23e6a9d97.ago@gentoo \
--to=ago@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