From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/traceroute/
Date: Sun, 3 Apr 2022 02:48:47 +0000 (UTC) [thread overview]
Message-ID: <1648954075.4dc334ecf0cb55f6f99986904ed6a09cc77aee4f.sam@gentoo> (raw)
commit: 4dc334ecf0cb55f6f99986904ed6a09cc77aee4f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 3 02:47:55 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Apr 3 02:47:55 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4dc334ec
net-analyzer/traceroute: adapt to iputils traceroute6 removal
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../{traceroute-2.1.0.ebuild => traceroute-2.1.0-r1.ebuild} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net-analyzer/traceroute/traceroute-2.1.0.ebuild b/net-analyzer/traceroute/traceroute-2.1.0-r1.ebuild
similarity index 91%
rename from net-analyzer/traceroute/traceroute-2.1.0.ebuild
rename to net-analyzer/traceroute/traceroute-2.1.0-r1.ebuild
index 5bc894ba920f..11338e0002b2 100644
--- a/net-analyzer/traceroute/traceroute-2.1.0.ebuild
+++ b/net-analyzer/traceroute/traceroute-2.1.0-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -15,7 +15,7 @@ KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~m68k ~mips ppc ppc64 ~riscv ~s390 s
IUSE="static"
RDEPEND="!<net-misc/iputils-20121221-r1
- !net-misc/iputils[traceroute6]"
+ !net-misc/iputils[traceroute6(-)]"
src_compile() {
use static && append-ldflags -static
next reply other threads:[~2022-04-03 2:48 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 2:48 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-01 18:54 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/traceroute/ John Helmert III
2024-02-08 7:44 Sam James
2024-02-03 6:56 Sam James
2024-02-02 13:45 Arthur Zamarin
2024-02-02 13:34 Arthur Zamarin
2024-02-02 6:40 Sam James
2024-02-02 3:58 Sam James
2023-12-24 17:21 Arthur Zamarin
2023-12-24 15:11 Sam James
2023-12-23 19:56 Arthur Zamarin
2023-12-20 10:04 Sam James
2023-08-31 5:29 Sam James
2023-05-01 13:36 Sam James
2023-03-04 17:54 Arthur Zamarin
2023-03-04 11:03 Arthur Zamarin
2023-03-04 9:55 Arthur Zamarin
2023-03-04 7:56 Arthur Zamarin
2023-03-04 6:17 Arthur Zamarin
2023-03-04 6:09 Arthur Zamarin
2023-03-04 5:32 Arthur Zamarin
2023-01-01 2:08 Sam James
2022-06-21 16:29 David Seifert
2022-05-26 5:06 WANG Xuerui
2021-09-23 1:07 Matt Turner
2021-07-16 1:31 Yixun Lan
2020-04-21 8:01 Jeroen Roovers
2019-03-31 22:37 Thomas Deutschmann
2019-01-29 11:52 Mikle Kolyada
2018-10-09 9:45 Mikle Kolyada
2018-10-06 23:47 Matt Turner
2018-10-06 23:47 Matt Turner
2018-10-02 20:10 Jeroen Roovers
2018-10-02 14:02 Tobias Klausmann
2018-10-01 0:07 Thomas Deutschmann
2018-09-30 23:03 Mart Raudsepp
2018-09-30 21:38 Sergei Trofimovich
2018-09-29 8:01 Sergei Trofimovich
2018-09-28 8:41 Mikle Kolyada
2016-03-09 8:02 Lars Wendler
2016-03-09 8:02 Lars Wendler
2016-02-19 1:58 Mike Frysinger
2016-02-19 1:58 Mike Frysinger
2016-02-19 1:58 Mike Frysinger
2016-02-19 1:58 Mike Frysinger
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=1648954075.4dc334ecf0cb55f6f99986904ed6a09cc77aee4f.sam@gentoo \
--to=sam@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