public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-python/markdown-include/
Date: Sat, 29 Oct 2022 05:54:42 +0000 (UTC)	[thread overview]
Message-ID: <1666993252.afd9b79df5292735a6baaa0f473ffc5469edce3e.arthurzam@gentoo> (raw)

commit:     afd9b79df5292735a6baaa0f473ffc5469edce3e
Author:     Sergey Torokhov <torokhov-s-a <AT> yandex <DOT> ru>
AuthorDate: Fri Oct 28 21:40:52 2022 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Fri Oct 28 21:40:52 2022 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=afd9b79d

dev-python/markdown-include: drop old 0.6.0

Signed-off-by: Sergey Torokhov <torokhov-s-a <AT> yandex.ru>

 dev-python/markdown-include/Manifest                   |  1 -
 .../markdown-include/markdown-include-0.6.0.ebuild     | 18 ------------------
 2 files changed, 19 deletions(-)

diff --git a/dev-python/markdown-include/Manifest b/dev-python/markdown-include/Manifest
index 1c8b04dfa..bc9ab5bb0 100644
--- a/dev-python/markdown-include/Manifest
+++ b/dev-python/markdown-include/Manifest
@@ -1,2 +1 @@
-DIST markdown-include-0.6.0.tar.gz 4661 BLAKE2B 449e05b40ab3a8725f68a8c02dc32349de2435520790b955b708c39ac53782c91dd6b592a712fafe9442f6ba1fda0794436500a5a4148d16caaf38dd6af8b69f SHA512 cbd83ff6ae64416410a7b6879c6f3fa4edd1b1d6e898508251651f0366bf7a121d2e0447f638069b84f872713dc9618128a4fa524d2eaddcfa8bfc2ed3be76de
 DIST markdown-include-0.7.0.gh.tar.gz 16696 BLAKE2B 0816c25afe73f0046d9cf56ad6a985bf76ebd7b4f78f64db631697ffcd07f9e0550b2dd74411945e38c27965153be186a89d82c55aa7bf4570be47c1cfca2917 SHA512 2d4350ad87cc7e5dab116f4df7648d3a7ffc0c18e38b61ddfca9a6cf76a64bd1d41dcbf7525fd41c81cbc64abe1f776cd3ad9847e25fe790f16c4a024265390d

diff --git a/dev-python/markdown-include/markdown-include-0.6.0.ebuild b/dev-python/markdown-include/markdown-include-0.6.0.ebuild
deleted file mode 100644
index 87f3bbcee..000000000
--- a/dev-python/markdown-include/markdown-include-0.6.0.ebuild
+++ /dev/null
@@ -1,18 +0,0 @@
-# Copyright 1999-2022 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-PYTHON_COMPAT=( python3_{8..10} )
-
-inherit distutils-r1
-
-DESCRIPTION="Syntax which allows for inclusion of contents of other Markdown docs"
-HOMEPAGE="https://github.com/cmacmackin/markdown-include"
-SRC_URI="mirror://pypi/${P:0:1}/${PN}/${P}.tar.gz"
-
-LICENSE="GPL-3"
-KEYWORDS="~amd64 ~x86"
-SLOT="0"
-
-RDEPEND="dev-python/markdown[${PYTHON_USEDEP}]"


             reply	other threads:[~2022-10-29  5:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29  5:54 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-09 17:57 [gentoo-commits] repo/proj/guru:master commit in: dev-python/markdown-include/ Ronny Gutbrod
2022-12-09 17:57 Ronny Gutbrod
2022-12-05  9:20 Viorel Munteanu
2021-09-07  2:58 Haelwenn Monnier
2021-05-24 11:06 Andrew Ammerlaan
2020-11-20 16:03 Andrew Ammerlaan
2020-04-28 17:30 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-04-29 11:12 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan

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=1666993252.afd9b79df5292735a6baaa0f473ffc5469edce3e.arthurzam@gentoo \
    --to=arthurzam@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