From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/pwndbg/
Date: Mon, 26 Dec 2022 10:19:35 +0000 (UTC) [thread overview]
Message-ID: <1672049911.102127e7f78210ed39f8b20beff2cf98e95d61cd.sam@gentoo> (raw)
commit: 102127e7f78210ed39f8b20beff2cf98e95d61cd
Author: Mario Haustein <mario.haustein <AT> hrz <DOT> tu-chemnitz <DOT> de>
AuthorDate: Mon Dec 26 10:02:58 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Dec 26 10:18:31 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=102127e7
dev-util/pwndbg: remove unnecessary dependencies
dev-python/future was never needed (see
https://github.com/pwndbg/pwndbg/issues/1250).
dev-python/isort is a development dependency only.
Closes: https://bugs.gentoo.org/888289
Signed-off-by: Mario Haustein <mario.haustein <AT> hrz.tu-chemnitz.de>
Closes: https://github.com/gentoo/gentoo/pull/28824
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/pwndbg/{pwndbg-20221219.ebuild => pwndbg-20221219-r1.ebuild} | 2 --
dev-util/pwndbg/pwndbg-99999999.ebuild | 2 --
2 files changed, 4 deletions(-)
diff --git a/dev-util/pwndbg/pwndbg-20221219.ebuild b/dev-util/pwndbg/pwndbg-20221219-r1.ebuild
similarity index 96%
rename from dev-util/pwndbg/pwndbg-20221219.ebuild
rename to dev-util/pwndbg/pwndbg-20221219-r1.ebuild
index 4f74956fcf62..bcd220f3d9af 100644
--- a/dev-util/pwndbg/pwndbg-20221219.ebuild
+++ b/dev-util/pwndbg/pwndbg-20221219-r1.ebuild
@@ -33,8 +33,6 @@ RDEPEND="
sys-devel/gdb[python,${PYTHON_SINGLE_USEDEP}]
$(python_gen_cond_dep '
dev-libs/capstone[python,${PYTHON_USEDEP}]
- dev-python/future[${PYTHON_USEDEP}]
- dev-python/isort[${PYTHON_USEDEP}]
dev-python/psutil[${PYTHON_USEDEP}]
dev-python/pycparser[${PYTHON_USEDEP}]
dev-python/pyelftools[${PYTHON_USEDEP}]
diff --git a/dev-util/pwndbg/pwndbg-99999999.ebuild b/dev-util/pwndbg/pwndbg-99999999.ebuild
index 4f74956fcf62..bcd220f3d9af 100644
--- a/dev-util/pwndbg/pwndbg-99999999.ebuild
+++ b/dev-util/pwndbg/pwndbg-99999999.ebuild
@@ -33,8 +33,6 @@ RDEPEND="
sys-devel/gdb[python,${PYTHON_SINGLE_USEDEP}]
$(python_gen_cond_dep '
dev-libs/capstone[python,${PYTHON_USEDEP}]
- dev-python/future[${PYTHON_USEDEP}]
- dev-python/isort[${PYTHON_USEDEP}]
dev-python/psutil[${PYTHON_USEDEP}]
dev-python/pycparser[${PYTHON_USEDEP}]
dev-python/pyelftools[${PYTHON_USEDEP}]
next reply other threads:[~2022-12-26 10:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 10:19 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-04 8:33 [gentoo-commits] repo/gentoo:master commit in: dev-util/pwndbg/ Sam James
2023-12-04 8:33 Sam James
2023-10-27 3:20 Sam James
2023-10-19 12:17 Sam James
2023-10-19 12:17 Sam James
2023-09-18 7:40 Sam James
2023-09-18 7:40 Sam James
2023-09-18 7:40 Sam James
2023-04-19 6:07 Sam James
2023-04-19 6:07 Sam James
2023-03-20 5:36 Sam James
2023-03-20 5:36 Sam James
2023-03-05 7:25 Joonas Niilola
2023-03-04 11:24 Arthur Zamarin
2023-01-31 2:01 Sam James
2023-01-31 2:01 Sam James
2023-01-27 10:11 Jakov Smolić
2023-01-27 6:31 Sam James
2022-12-21 19:29 Sam James
2022-12-10 4:35 Sam James
2022-09-30 20:39 Sam James
2022-09-30 20:39 Sam James
2022-08-31 1:24 Sam James
2022-08-27 16:03 Sam James
2022-04-05 3:33 Sam James
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=1672049911.102127e7f78210ed39f8b20beff2cf98e95d61cd.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