From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/tcptrace/
Date: Thu, 28 Dec 2017 12:40:07 +0000 (UTC) [thread overview]
Message-ID: <1514464798.c4b373aa70ee4637d3129a6a741130408125869d.slyfox@gentoo> (raw)
commit: c4b373aa70ee4637d3129a6a741130408125869d
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Thu Dec 28 12:39:58 2017 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Thu Dec 28 12:39:58 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c4b373aa
net-analyzer/tcptrace: stable 6.6.7_p4_p1 for ppc64, bug #640008
Package-Manager: Portage-2.3.19, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc64"
net-analyzer/tcptrace/tcptrace-6.6.7_p4_p1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-analyzer/tcptrace/tcptrace-6.6.7_p4_p1.ebuild b/net-analyzer/tcptrace/tcptrace-6.6.7_p4_p1.ebuild
index a52be3ee94e..e0a0ede25bf 100644
--- a/net-analyzer/tcptrace/tcptrace-6.6.7_p4_p1.ebuild
+++ b/net-analyzer/tcptrace/tcptrace-6.6.7_p4_p1.ebuild
@@ -20,7 +20,7 @@ SRC_URI="
SLOT="0"
LICENSE="GPL-2"
-KEYWORDS="amd64 ~ppc ~ppc64 ~x86"
+KEYWORDS="amd64 ~ppc ppc64 ~x86"
DEPEND="
net-libs/libpcap
next reply other threads:[~2017-12-28 12:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 12:40 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-29 7:51 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/tcptrace/ Jakov Smolić
2024-03-20 6:26 Sam James
2024-03-20 6:26 Sam James
2023-11-04 13:35 Sam James
2023-11-04 13:35 Sam James
2023-11-04 12:25 Sam James
2022-09-30 23:24 Sam James
2021-03-16 14:48 Sam James
2021-03-16 14:47 Sam James
2021-03-15 21:55 Sam James
2021-03-15 21:53 Sam James
2020-09-30 9:49 Jeroen Roovers
2018-02-08 19:48 Jeroen Roovers
2017-12-19 8:32 Jason Zaman
2016-07-30 19:28 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=1514464798.c4b373aa70ee4637d3129a6a741130408125869d.slyfox@gentoo \
--to=slyfox@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