From: "Andrew Ammerlaan" <andrewammerlaan@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-python/schedule/
Date: Sun, 28 Mar 2021 09:55:11 +0000 (UTC) [thread overview]
Message-ID: <1616924894.fc318e925ff23390bfd3cda1e7fa91f2c2772696.andrewammerlaan@gentoo> (raw)
commit: fc318e925ff23390bfd3cda1e7fa91f2c2772696
Author: Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
AuthorDate: Sun Mar 28 09:48:14 2021 +0000
Commit: Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
CommitDate: Sun Mar 28 09:48:14 2021 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=fc318e92
dev-python/schedule: drop old
Package-Manager: Portage-3.0.17, Repoman-3.0.2
Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> riseup.net>
dev-python/schedule/Manifest | 1 -
dev-python/schedule/schedule-0.6.0-r1.ebuild | 35 ----------------------------
2 files changed, 36 deletions(-)
diff --git a/dev-python/schedule/Manifest b/dev-python/schedule/Manifest
index 9fd6b2d98..314d09258 100644
--- a/dev-python/schedule/Manifest
+++ b/dev-python/schedule/Manifest
@@ -1,2 +1 @@
-DIST schedule-0.6.0.tar.gz 21671 BLAKE2B 6076aff0c906782e554175b7e90cfca1417a31170e99009caccb5cbe318b5eb1295b24dfe1835109aec78fee53b615e170f03a7ec4470f596a9a2775c1072d5f SHA512 48424707b57cbc7ce9440e1658784347b691a013552b9969fd95dd260efa2d8ba56b41920628540fc4ebebbc3dc78e8e919b83cfddfe9a3cc3d60ece6ef0998f
DIST schedule-1.0.0.tar.gz 27992 BLAKE2B 620afa1d78065f189799e4deaae8a627d1698292cf885acdacdfd6688b8774ed155a13c8213bb0f6dfd70dec5e17ea317658f5d78e6cbdc87d670003c218e154 SHA512 79e350d5e5083bb6da70bbd12f4e8895a08fc79088f042fa9171aec48b8a45985f1638511136be2ee8f4aa92d6992978f8c85560867b6fa88a07383e952c8c4b
diff --git a/dev-python/schedule/schedule-0.6.0-r1.ebuild b/dev-python/schedule/schedule-0.6.0-r1.ebuild
deleted file mode 100644
index 55e196536..000000000
--- a/dev-python/schedule/schedule-0.6.0-r1.ebuild
+++ /dev/null
@@ -1,35 +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} )
-
-inherit distutils-r1
-
-DESCRIPTION="Python job scheduling for humans"
-HOMEPAGE="https://github.com/dbader/schedule"
-
-if [[ ${PV} = 9999* ]]; then
- EGIT_REPO_URI="https://github.com/dbader/schedule"
- EGIT_BRANCH="master"
- inherit git-r3
- KEYWORDS=""
-else
- SRC_URI="https://github.com/dbader/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
- KEYWORDS="~amd64 ~arm ~arm64 ~x86"
-fi
-
-LICENSE="MIT"
-SLOT="0"
-
-RDEPEND=""
-DEPEND="
- test? (
- >=dev-python/mock-2.0.0[${PYTHON_USEDEP}]
- >=dev-python/pytest-3.0.3[${PYTHON_USEDEP}]
- )
-"
-
-distutils_enable_tests pytest
-distutils_enable_sphinx docs
next reply other threads:[~2021-03-28 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 9:55 Andrew Ammerlaan [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-29 21:04 [gentoo-commits] repo/proj/guru:dev commit in: dev-python/schedule/ Alessandro Barbieri
2021-06-14 23:09 Alessandro Barbieri
2021-05-09 0:35 Alessandro Barbieri
2021-03-27 18:35 Alessandro Barbieri
2021-03-27 18:35 Alessandro Barbieri
2020-04-07 1:22 Alessandro Barbieri
2020-04-07 1:22 Alessandro Barbieri
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=1616924894.fc318e925ff23390bfd3cda1e7fa91f2c2772696.andrewammerlaan@gentoo \
--to=andrewammerlaan@riseup.net \
--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