public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "John Helmert III" <ajak@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/cutter/
Date: Sun, 16 Apr 2023 18:52:15 +0000 (UTC)	[thread overview]
Message-ID: <1681668577.f8c2fc4c76730eec2b136227d7c0468f1e91a871.ajak@gentoo> (raw)

commit:     f8c2fc4c76730eec2b136227d7c0468f1e91a871
Author:     John Helmert III <ajak <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 16 18:08:30 2023 +0000
Commit:     John Helmert III <ajak <AT> gentoo <DOT> org>
CommitDate: Sun Apr 16 18:09:37 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f8c2fc4c

dev-util/cutter: fix file collision with net-analyzer/cutter

Closes: https://bugs.gentoo.org/897738
Signed-off-by: John Helmert III <ajak <AT> gentoo.org>

 dev-util/cutter/{cutter-2.2.0.ebuild => cutter-2.2.0-r1.ebuild} | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/dev-util/cutter/cutter-2.2.0.ebuild b/dev-util/cutter/cutter-2.2.0-r1.ebuild
similarity index 94%
rename from dev-util/cutter/cutter-2.2.0.ebuild
rename to dev-util/cutter/cutter-2.2.0-r1.ebuild
index a50f8070c0da..2ced0df3a4d9 100644
--- a/dev-util/cutter/cutter-2.2.0.ebuild
+++ b/dev-util/cutter/cutter-2.2.0-r1.ebuild
@@ -28,7 +28,8 @@ DEPEND="${PYTHON_DEPS}
 	dev-qt/qtwidgets:5
 	>=dev-util/rizin-0.5.0:=
 	graphviz? ( media-gfx/graphviz )"
-RDEPEND="${DEPEND}"
+RDEPEND="${DEPEND}
+	!net-analyzer/cutter" # https://bugs.gentoo.org/897738
 BDEPEND="dev-qt/linguist-tools:5"
 
 src_configure() {


             reply	other threads:[~2023-04-16 18:52 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 18:52 John Helmert III [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-28 18:51 [gentoo-commits] repo/gentoo:master commit in: dev-util/cutter/ John Helmert III
2024-07-28 18:51 John Helmert III
2024-07-28  2:39 Sam James
2024-05-11 19:08 Sam James
2024-04-21 23:33 John Helmert III
2024-03-04  5:21 John Helmert III
2024-03-04  5:21 John Helmert III
2023-09-26  0:54 Sam James
2023-09-17  0:06 John Helmert III
2023-09-10 18:04 John Helmert III
2023-07-22 16:30 John Helmert III
2023-07-22 16:30 John Helmert III
2023-07-22 16:30 John Helmert III
2023-06-02  4:04 John Helmert III
2023-04-30 23:36 John Helmert III
2023-04-30 23:36 John Helmert III
2023-02-25 16:35 John Helmert III
2023-02-23  3:55 John Helmert III
2023-02-22 15:58 John Helmert III
2022-10-21 19:56 John Helmert III
2022-10-21 19:56 John Helmert III
2022-09-11 13:33 John Helmert III
2022-09-10 21:22 John Helmert III
2022-08-08  9:40 Andreas Sturmlechner
2022-07-04 20:01 John Helmert III
2022-07-04 20:01 John Helmert III
2022-07-04 20:01 John Helmert III
2022-03-02  2:43 John Helmert III
2022-03-02  2:43 John Helmert III
2022-01-14 20:35 John Helmert III
2021-12-01 16:22 John Helmert III
2021-11-20 23:30 John Helmert III
2021-10-17 16:08 John Helmert III
2021-10-15 16:57 Rick Farina
2021-10-05 20:40 John Helmert III
2021-05-24 23:37 John Helmert III
2021-05-24 23:37 John Helmert III
2021-04-27  3:15 John Helmert III
2021-04-14 19:26 John Helmert III
2021-04-11 22:31 John Helmert III
2021-04-06 19:03 Sergei Trofimovich
2021-04-06 13:08 John Helmert III
2021-04-06  2:59 John Helmert III
2020-10-18 12:31 Sergei Trofimovich
2020-09-03 22:28 Sergei Trofimovich
2020-07-25  5:44 Joonas Niilola
2020-07-25  5:30 Joonas Niilola
2020-07-25  5:30 Joonas Niilola
2020-07-25  5:30 Joonas Niilola
2020-07-24  8:28 Joonas Niilola
2019-08-12 20:16 Michał Górny
2019-07-07 19:17 Michał Górny
2018-01-25 11:16 Michael Palimaka

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=1681668577.f8c2fc4c76730eec2b136227d7c0468f1e91a871.ajak@gentoo \
    --to=ajak@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