public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-forensics/volatility3/
Date: Wed, 19 Feb 2025 11:14:01 +0000 (UTC)	[thread overview]
Message-ID: <1739963527.4d8c44e876a99c7fabd6b021881afa89008b5511.sam@gentoo> (raw)

commit:     4d8c44e876a99c7fabd6b021881afa89008b5511
Author:     Mario Haustein <mario.haustein <AT> hrz <DOT> tu-chemnitz <DOT> de>
AuthorDate: Thu Jan 16 21:46:15 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Feb 19 11:12:07 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4d8c44e8

app-forensics/volatility3: limit dev-libs/capstone to compatible versions

Capstone 6 is not supported (see
https://github.com/volatilityfoundation/volatility3/issues/1336).

Signed-off-by: Mario Haustein <mario.haustein <AT> hrz.tu-chemnitz.de>
Closes: https://github.com/gentoo/gentoo/pull/40168
Signed-off-by: Sam James <sam <AT> gentoo.org>

 .../{volatility3-2.8.0.ebuild => volatility3-2.8.0-r1.ebuild}       | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/app-forensics/volatility3/volatility3-2.8.0.ebuild b/app-forensics/volatility3/volatility3-2.8.0-r1.ebuild
similarity index 94%
rename from app-forensics/volatility3/volatility3-2.8.0.ebuild
rename to app-forensics/volatility3/volatility3-2.8.0-r1.ebuild
index f0db988c8286..a58558f50c2c 100644
--- a/app-forensics/volatility3/volatility3-2.8.0.ebuild
+++ b/app-forensics/volatility3/volatility3-2.8.0-r1.ebuild
@@ -31,7 +31,11 @@ IUSE="crypt disasm jsonschema leechcore snappy test yara"
 RDEPEND="
 	>=dev-python/pefile-2023.2.7[${PYTHON_USEDEP}]
 	crypt? ( >=dev-python/pycryptodome-3[${PYTHON_USEDEP}] )
-	disasm? ( >=dev-libs/capstone-3.0.5[python,${PYTHON_USEDEP}] )
+	disasm?
+	(
+		>=dev-libs/capstone-3.0.5[python,${PYTHON_USEDEP}]
+		<dev-libs/capstone-6[python,${PYTHON_USEDEP}]
+	)
 	jsonschema? ( >=dev-python/jsonschema-2.3.0[${PYTHON_USEDEP}] )
 	leechcore? ( >=dev-python/leechcorepyc-2.4.0[${PYTHON_USEDEP}] )
 	snappy? ( app-arch/snappy:0/1.1 )


             reply	other threads:[~2025-02-19 11:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19 11:14 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-28  6:53 [gentoo-commits] repo/gentoo:master commit in: app-forensics/volatility3/ Arthur Zamarin
2025-03-22  9:20 Arthur Zamarin
2025-02-19 22:21 Sam James
2025-02-19 22:21 Sam James
2025-02-19 11:14 Sam James
2025-02-19 11:14 Sam James
2025-01-12 13:16 Sam James
2025-01-12 13:16 Sam James
2024-12-01 12:42 Sam James
2024-12-01 12:42 Sam James
2024-12-01 12:42 Sam James
2024-06-30 19:41 Sam James
2024-06-30 18:34 Arthur Zamarin
2024-05-30 15:01 Arthur Zamarin
2024-04-24 17:24 Arthur Zamarin
2024-04-23 20:38 Sam James
2024-03-08  9:44 Arthur Zamarin
2023-09-18  7:40 Sam James
2023-09-18  7:40 Sam James
2023-09-17  5:19 Arthur Zamarin
2023-05-26  7:15 Sam James
2023-05-01  8:34 Sam James
2023-05-01  8:34 Sam James
2023-04-25  1:57 Sam James
2023-02-25 22:23 Sam James
2022-12-16 22:57 Sam James
2022-12-16 22:57 Sam James
2022-12-15  4:44 Sam James
2022-08-04 22:53 Sam James
2022-08-04 22:53 Sam James
2022-04-10 17:01 Sam James
2022-04-05  3:33 Sam James
2022-04-05  3:33 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=1739963527.4d8c44e876a99c7fabd6b021881afa89008b5511.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