From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/mkdocs-redirects/
Date: Sat,  6 Jul 2024 17:58:41 +0000 (UTC)	[thread overview]
Message-ID: <1720288711.c1a64a91d4903b41ca4be560dd8be6b81a5d5d6b.mgorny@gentoo> (raw)
commit:     c1a64a91d4903b41ca4be560dd8be6b81a5d5d6b
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sat Jul  6 17:45:37 2024 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sat Jul  6 17:58:31 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c1a64a91
dev-python/mkdocs-redirects: Remove incorrect dev-python/twine dep
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
 ...{mkdocs-redirects-1.2.1.ebuild => mkdocs-redirects-1.2.1-r1.ebuild} | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/dev-python/mkdocs-redirects/mkdocs-redirects-1.2.1.ebuild b/dev-python/mkdocs-redirects/mkdocs-redirects-1.2.1-r1.ebuild
similarity index 90%
rename from dev-python/mkdocs-redirects/mkdocs-redirects-1.2.1.ebuild
rename to dev-python/mkdocs-redirects/mkdocs-redirects-1.2.1-r1.ebuild
index 6e9f661ea205..b6cd149bbfe2 100644
--- a/dev-python/mkdocs-redirects/mkdocs-redirects-1.2.1.ebuild
+++ b/dev-python/mkdocs-redirects/mkdocs-redirects-1.2.1-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -25,7 +25,6 @@ RDEPEND="
 	>=dev-python/mkdocs-1.0.4[${PYTHON_USEDEP}]
 	<dev-python/mkdocs-2[${PYTHON_USEDEP}]
 	dev-python/six[${PYTHON_USEDEP}]
-	dev-python/twine[${PYTHON_USEDEP}]
 "
 
 distutils_enable_tests pytest
next             reply	other threads:[~2024-07-06 17:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-06 17:58 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-27 21:01 [gentoo-commits] repo/gentoo:master commit in: dev-python/mkdocs-redirects/ Michał Górny
2024-11-23 10:08 Michał Górny
2024-11-23  9:52 Sam James
2024-11-08  4:52 Michał Górny
2024-07-06 17:58 Michał Górny
2023-11-25  5:18 Sam James
2023-11-22 12:43 Andrew Ammerlaan
2023-09-14  9:58 Andrew Ammerlaan
2023-08-19 18:19 Michał Górny
2023-08-19 17:53 Arthur Zamarin
2023-07-19  6:57 Michał Górny
2023-04-14 19:43 Sam James
2023-04-14  4:04 Sam James
2023-02-25  5:47 Arthur Zamarin
2022-10-25 12:12 Michał Górny
2022-10-25 10:44 Sam James
2022-09-26  6:06 Michał Górny
2022-09-26  6:06 Michał Górny
2022-09-22 10:55 Andrew Ammerlaan
2022-09-07  5:03 Michał Górny
2022-09-06 21:12 Sam James
2022-08-22 19:23 Arthur Zamarin
2022-08-03 17:30 Arthur Zamarin
2022-06-06  9:53 Michał Górny
2022-06-06  9:29 Jakov Smolić
2022-05-24 13:02 Andrew Ammerlaan
2022-05-02 10:18 Andrew Ammerlaan
2022-05-02 10:18 Andrew Ammerlaan
2021-11-14  8:52 Michał Górny
2021-11-12  8:43 Marek Szuba
2021-10-17  9:07 Michał Górny
2021-10-15 23:15 Sam James
2021-09-09 15:51 Arthur Zamarin
2021-09-09 15:17 Marek Szuba
2021-07-13  6:34 Agostino Sarubbo
2021-07-13  0:05 Sam James
2021-06-11 14:05 Andrew Ammerlaan
2021-04-13 11:07 Joonas Niilola
2020-12-08  5:53 Joonas Niilola
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=1720288711.c1a64a91d4903b41ca4be560dd8be6b81a5d5d6b.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