From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-forensics/volatility3/
Date: Mon, 18 Sep 2023 07:40:49 +0000 (UTC) [thread overview]
Message-ID: <1695022755.5e0d2e41af3a837a230246f1bcadffa7617ee584.sam@gentoo> (raw)
commit: 5e0d2e41af3a837a230246f1bcadffa7617ee584
Author: Mario Haustein <mario.haustein <AT> hrz <DOT> tu-chemnitz <DOT> de>
AuthorDate: Sat Sep 16 08:54:29 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Sep 18 07:39:15 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5e0d2e41
app-forensics/volatility3: drop 2.0.1
Signed-off-by: Mario Haustein <mario.haustein <AT> hrz.tu-chemnitz.de>
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-forensics/volatility3/Manifest | 1 -
app-forensics/volatility3/volatility3-2.0.1.ebuild | 31 ----------------------
2 files changed, 32 deletions(-)
diff --git a/app-forensics/volatility3/Manifest b/app-forensics/volatility3/Manifest
index 54c064311846..4354462bc137 100644
--- a/app-forensics/volatility3/Manifest
+++ b/app-forensics/volatility3/Manifest
@@ -1,4 +1,3 @@
-DIST volatility3-2.0.1.tar.gz 427679 BLAKE2B eb9b4ebb885a8dd4de2769c666b503da4bef792389efbf487815808fd514cf84f7f10b5a12926cf398a4028e7b72a5b78892c4c92d3709fea37fe13a6f32af7d SHA512 752b3fc23b3668df4329f6dbefa2ff8eb2dd63bc6e22e18774096cebae93053567727e3dc6e5ecbf7a0731459c829c37cea8ac735564c62f96a4f652ad2b6cb9
DIST volatility3-2.4.0.gh.tar.gz 464123 BLAKE2B 436f0996b7c1d997727885949941fdaff3d801dbd5182ec9332d6f8182fc9bb56b91b50aad11f901e84bf4f3399f7ac0a61d484cd57fc36d7baf106ffcdb8fbd SHA512 03d74ff1c34a583dfc6a43fdb94947e4bd691e92a7f6a52d7323388edb47e955c06db523c21d9969012a4c607896daa8f20d82393d4ec457ebbf8c09b6537d25
DIST volatility3-2.4.1.gh.tar.gz 486648 BLAKE2B 7f00ec6b57eb9ef6420f4c1aa735203fbd51fca39aa13200eb821d13842f879c8743f63da7c5bbcf7d84a2850709a15c0aadc2b0311edbdf34dfa026f2a3dcd6 SHA512 5f785a778654b76fc85b7b82b2e9ba9e6315a99169d4d956a9af84ae91086e7a38cac343b7df0f00d6830361c77d377408bf8eab3679c161c8a02212c696389c
DIST volatility3-linux-sample-1.bin.gz 143967523 BLAKE2B 3321e991a50b6e4ccf19e0ee48d779664f43f4cdbdb950ca31a5d08c8ee9de0018e2d4f69f42206f7e8f1c6ea735c47f8aa42806ed0f85e9a837b611f07b3289 SHA512 82a34aa1d4e7d7deb9ea12e892f14ba0a28908b2da2e31ca76efd1e9e59d87769064a1ffffe8979a58b992cea7005fa20954df50984dbe1dd186513ad95168d7
diff --git a/app-forensics/volatility3/volatility3-2.0.1.ebuild b/app-forensics/volatility3/volatility3-2.0.1.ebuild
deleted file mode 100644
index 1e78c0d472f9..000000000000
--- a/app-forensics/volatility3/volatility3-2.0.1.ebuild
+++ /dev/null
@@ -1,31 +0,0 @@
-# Copyright 1999-2023 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-DISTUTILS_USE_PEP517=setuptools
-PYTHON_COMPAT=( python3_{9..10} )
-inherit distutils-r1
-
-MY_PV=${PV//_beta/-beta.}
-
-DESCRIPTION="Framework for analyzing volatile memory"
-HOMEPAGE="https://github.com/volatilityfoundation/volatility3/ https://www.volatilityfoundation.org/"
-SRC_URI="https://github.com/volatilityfoundation/volatility3/archive/v${MY_PV}.tar.gz -> ${P}.tar.gz"
-S="${WORKDIR}"/${PN}-${MY_PV}
-
-LICENSE="GPL-2+"
-SLOT="0"
-KEYWORDS="amd64 x86"
-IUSE="crypt disasm jsonschema leechcore snappy yara"
-
-RDEPEND="
- >=dev-python/pefile-2017.8.1[${PYTHON_USEDEP}]
- crypt? ( >=dev-python/pycryptodome-3[${PYTHON_USEDEP}] )
- disasm? ( >=dev-libs/capstone-3.0.5[python,${PYTHON_USEDEP}] )
- jsonschema? ( >=dev-python/jsonschema-2.3.0[${PYTHON_USEDEP}] )
- leechcore? ( >=dev-python/leechcorepyc-2.4.0[${PYTHON_USEDEP}] )
- snappy? ( >=dev-python/python-snappy-0.6.0[${PYTHON_USEDEP}] )
- yara? ( >=dev-python/yara-python-3.8.0[${PYTHON_USEDEP}] )
-"
-DEPEND="${RDEPEND}"
next reply other threads:[~2023-09-18 7:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 7:40 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-22 9:20 [gentoo-commits] repo/gentoo:master commit in: app-forensics/volatility3/ 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-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-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=1695022755.5e0d2e41af3a837a230246f1bcadffa7617ee584.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