From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pyprof2calltree/
Date: Fri, 7 May 2021 11:11:07 +0000 (UTC) [thread overview]
Message-ID: <1620385854.b623cd5e336af0fa82e96ccab3842d030e0e8689.mgorny@gentoo> (raw)
commit: b623cd5e336af0fa82e96ccab3842d030e0e8689
Author: Jakov Smolic <jakov.smolic <AT> sartura <DOT> hr>
AuthorDate: Thu May 6 23:10:10 2021 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Fri May 7 11:10:54 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b623cd5e
dev-python/pyprof2calltree: Remove old 1.4.4
Signed-off-by: Jakov Smolic <jakov.smolic <AT> sartura.hr>
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/pyprof2calltree/Manifest | 1 -
.../pyprof2calltree/pyprof2calltree-1.4.4.ebuild | 19 -------------------
2 files changed, 20 deletions(-)
diff --git a/dev-python/pyprof2calltree/Manifest b/dev-python/pyprof2calltree/Manifest
index 8b4e2849240..cbeea65c4c4 100644
--- a/dev-python/pyprof2calltree/Manifest
+++ b/dev-python/pyprof2calltree/Manifest
@@ -1,2 +1 @@
-DIST pyprof2calltree-1.4.4.tar.gz 8797 BLAKE2B 0929728d3a6de1cc40e54bd4581bb4b64875a4d7f3ccef725300d40d2b3fd175d8ff462591357e32a471e5c3a4c5c51ac7e9c81c2e857050745a748bc4117d8a SHA512 7ffc228e542a568cb421394035660623415495472b5b3659a35b02c7ccccb7f578dc872d2bb1daf4fdfcd44134e1ad9b5ce3a18f49b15dd4aeb3b5f1201a28d8
DIST pyprof2calltree-1.4.5.tar.gz 8806 BLAKE2B 3a8a838a8b03294504c64dbe1d0caee2606a1ec53005222dfe6c3692bacd0801041ce199fedb9c38e4f6edc91e210116d9c1e034e0aa283cafebb19bf6303fed SHA512 2fcda74ae67dc3a8abb5dc153864ef59f96cc62b1c9359d02be12e83966c17738f5aa4a3d1c6e2ff81614dc963fc4b2faf375bbbb1ad15650a6817e493cdde39
diff --git a/dev-python/pyprof2calltree/pyprof2calltree-1.4.4.ebuild b/dev-python/pyprof2calltree/pyprof2calltree-1.4.4.ebuild
deleted file mode 100644
index e24e2f0a715..00000000000
--- a/dev-python/pyprof2calltree/pyprof2calltree-1.4.4.ebuild
+++ /dev/null
@@ -1,19 +0,0 @@
-# Copyright 1999-2020 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=7
-PYTHON_COMPAT=( python3_{7,8} )
-DISTUTILS_USE_SETUPTOOLS=rdepend
-
-inherit distutils-r1
-
-DESCRIPTION="convert python profile data to kcachegrind calltree form"
-HOMEPAGE="https://pypi.org/project/pyprof2calltree/"
-# pypi tarball lacks tests
-SRC_URI="https://github.com/pwaller/pyprof2calltree/archive/v${PV}.tar.gz -> ${P}.tar.gz"
-
-LICENSE="MIT"
-SLOT="0"
-KEYWORDS="~amd64 ~x86"
-
-distutils_enable_tests setup.py
next reply other threads:[~2021-05-07 11:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 11:11 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-08 6:26 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyprof2calltree/ Sam James
2024-10-08 6:26 Sam James
2024-10-08 6:26 Sam James
2024-10-08 6:24 Sam James
2023-11-23 18:55 Michał Górny
2023-10-20 14:05 Michał Górny
2022-06-16 8:08 Michał Górny
2022-05-28 18:35 Arthur Zamarin
2022-05-28 18:35 Arthur Zamarin
2021-05-07 11:11 Michał Górny
2021-02-11 5:11 Sam James
2021-02-11 5:11 Sam James
2021-02-11 5:11 Sam James
2018-01-05 23:19 Michał Górny
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=1620385854.b623cd5e336af0fa82e96ccab3842d030e0e8689.mgorny@gentoo \
--to=mgorny@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