From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/mkdocs-i18n/
Date: Wed, 29 Nov 2023 11:38:38 +0000 (UTC) [thread overview]
Message-ID: <1701257881.e54ec8360566d828657b80bba6d1b3a687e6e20c.mgorny@gentoo> (raw)
commit: e54ec8360566d828657b80bba6d1b3a687e6e20c
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 29 11:38:01 2023 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Nov 29 11:38:01 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e54ec836
dev-python/mkdocs-i18n: Remove old
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/mkdocs-i18n/Manifest | 1 -
dev-python/mkdocs-i18n/mkdocs-i18n-0.4.5.ebuild | 25 -------------------------
2 files changed, 26 deletions(-)
diff --git a/dev-python/mkdocs-i18n/Manifest b/dev-python/mkdocs-i18n/Manifest
index 70edccec5210..af08ed144387 100644
--- a/dev-python/mkdocs-i18n/Manifest
+++ b/dev-python/mkdocs-i18n/Manifest
@@ -1,2 +1 @@
-DIST mkdocs-i18n-0.4.5.tar.gz 17228 BLAKE2B 19d6af2d96cd67d4b39e210f20113e75a6c47a413639f2d6c218cbf11709f91197d79df2c0ecfffe8a2e0912613178564e73eccdf15cece82d71b0639641940e SHA512 18c28704d1d0e294dfcfef402959e502c96b0e8fe346ba3f0c2ff49d70a67f3fe1254fcd1bcbf4217182e946b9f86f61d8d5b9c9475334c6f464feb696d0134e
DIST mkdocs-i18n-0.4.6.tar.gz 24232 BLAKE2B ba5f1462aa8c16fc97f7240875b6762e8072b3a4077b3324ab902a70930431c81512b465037f3a0fbd080716126ff185f78fc3f25b23ec352096628acc9bffab SHA512 f92ae260b8a2bf93d18ddd7d405354ab4227940fa820ef6a12427a167cd288bb25fcc53d805df38d2a7fe2621eb9ca62bd6a64bd1706d55638368b9b69429b9d
diff --git a/dev-python/mkdocs-i18n/mkdocs-i18n-0.4.5.ebuild b/dev-python/mkdocs-i18n/mkdocs-i18n-0.4.5.ebuild
deleted file mode 100644
index 6afd004add19..000000000000
--- a/dev-python/mkdocs-i18n/mkdocs-i18n-0.4.5.ebuild
+++ /dev/null
@@ -1,25 +0,0 @@
-# Copyright 1999-2023 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-DISTUTILS_USE_PEP517="setuptools"
-PYPI_NO_NORMALIZE=1
-PYTHON_COMPAT=( python3_{9..11} )
-
-inherit distutils-r1 pypi
-
-DESCRIPTION="MkDocs i18n plugin"
-HOMEPAGE="
- https://gitlab.com/mkdocs-i18n/mkdocs-i18n/-/tree/main
- https://pypi.org/project/mkdocs-i18n/
-"
-
-LICENSE="AGPL-3"
-SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~ppc ~ppc64 ~riscv x86"
-
-RDEPEND="
- >=dev-python/mkdocs-1.1[${PYTHON_USEDEP}]
- dev-python/mkdocs-material[${PYTHON_USEDEP}]
-"
next reply other threads:[~2023-11-29 11:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 11:38 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-02 11:02 [gentoo-commits] repo/gentoo:master commit in: dev-python/mkdocs-i18n/ Nowa Ammerlaan
2023-12-04 14:01 Michał Górny
2023-11-29 11:32 Michał Górny
2023-11-10 12:44 Andrew Ammerlaan
2023-05-29 4:37 Michał Górny
2023-05-28 20:03 Arthur Zamarin
2023-04-26 5:36 Michał Górny
2023-04-14 19:43 Sam James
2023-04-14 4:04 Sam James
2023-02-25 5:47 Arthur Zamarin
2023-01-14 10:00 Arthur Zamarin
2022-05-24 13:02 Andrew Ammerlaan
2022-03-27 17:17 Arthur Zamarin
2022-03-27 6:27 Agostino Sarubbo
2022-02-22 22:18 Yixun Lan
2022-02-22 19:53 Jakov Smolić
2022-02-21 19:31 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=1701257881.e54ec8360566d828657b80bba6d1b3a687e6e20c.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