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/gentoo:master commit in: dev-python/numpydoc/
Date: Thu, 10 Nov 2022 19:03:35 +0000 (UTC)	[thread overview]
Message-ID: <1668107003.a9c88b65ca1f9b2a251ee542040570f361ba0b6a.arthurzam@gentoo> (raw)

commit:     a9c88b65ca1f9b2a251ee542040570f361ba0b6a
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Thu Nov 10 19:03:23 2022 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Thu Nov 10 19:03:23 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a9c88b65

dev-python/numpydoc: Stabilize 1.5.0 ALLARCHES, #880779

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 dev-python/numpydoc/numpydoc-1.5.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/numpydoc/numpydoc-1.5.0.ebuild b/dev-python/numpydoc/numpydoc-1.5.0.ebuild
index e031076473c2..6b4a6e0d9159 100644
--- a/dev-python/numpydoc/numpydoc-1.5.0.ebuild
+++ b/dev-python/numpydoc/numpydoc-1.5.0.ebuild
@@ -21,7 +21,7 @@ SRC_URI="
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~x64-macos"
+KEYWORDS="amd64 arm arm64 hppa ~ia64 ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86 ~x64-macos"
 
 RDEPEND="
 	>=dev-python/jinja-2.10[${PYTHON_USEDEP}]


             reply	other threads:[~2022-11-10 19:03 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 19:03 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-24 13:06 [gentoo-commits] repo/gentoo:master commit in: dev-python/numpydoc/ Michał Górny
2024-08-24  8:10 Sam James
2024-08-10  5:26 Michał Górny
2024-07-25  3:12 Michał Górny
2024-06-30 11:51 Petr Vaněk
2024-05-27 15:30 Michał Górny
2024-04-13 16:01 Arthur Zamarin
2024-03-30  5:53 Michał Górny
2023-11-10  5:47 Viorel Munteanu
2023-10-28 15:23 Michał Górny
2023-10-28 15:23 Michał Górny
2023-10-27 19:32 Sam James
2023-09-26  4:42 Michał Górny
2022-11-10 19:25 Arthur Zamarin
2022-10-10 14:04 Michał Górny
2022-08-31 12:38 Andrew Ammerlaan
2022-07-10 19:09 Michał Górny
2022-07-10 16:58 Sam James
2022-06-10  8:25 Michał Górny
2022-05-27 19:53 Michał Górny
2022-05-27  9:21 Jakov Smolić
2022-05-01  6:41 Michał Górny
2022-04-30  7:35 Michał Górny
2022-04-26 10:56 Michał Górny
2022-04-15  6:52 Sam James
2022-03-15 14:17 Michał Górny
2022-03-15 12:33 Jakov Smolić
2022-01-29 22:13 James Le Cuirot
2022-01-24 22:14 Michał Górny
2022-01-17  5:33 Joshua Kinard
2021-11-18  8:10 Sam James
2021-11-14 20:35 Sam James
2021-10-14 12:12 Arthur Zamarin
2021-10-14 12:12 Arthur Zamarin
2021-09-08 16:19 Sam James
2021-09-06  0:18 Sam James
2021-06-20  1:55 Sam James
2021-05-31 20:31 Michał Górny
2020-11-29 21:02 Sam James
2020-08-14  5:10 Sam James
2020-07-09 13:01 Michał Górny
2020-07-05  6:09 Michał Górny
2020-06-08 20:18 Michał Górny
2020-06-01 20:30 Michał Górny
2020-05-30 19:48 Michał Górny
2020-05-30 16:20 Michał Górny
2020-05-30  8:56 Michał Górny
2020-05-29 17:23 Michał Górny
2020-05-18 10:40 Michał Górny
2020-04-26  3:12 Patrick McLean
2020-03-25 13:25 Michał Górny
2020-03-25 13:25 Michał Górny
2020-02-26 17:50 Rick Farina
2020-02-26 17:32 Rick Farina
2020-01-29 16:26 Michał Górny
2019-12-03  3:02 Aaron Bauman
2019-05-02 15:11 Virgil Dupras
2019-04-27 18:50 Virgil Dupras
2018-02-25 21:52 Sergei Trofimovich
2017-07-17 13:29 Alexis Ballier
2017-06-28  4:02 Sebastien Fabbro
2017-05-03  7:37 Michał Górny
2017-03-16  7:06 Michael Weber
2017-03-12 12:31 Zac Medico
2017-02-02 18:43 David Seifert
2017-01-29 17:15 Fabian Groffen
2017-01-22 15:01 Agostino Sarubbo
2017-01-21 18:54 Agostino Sarubbo
2016-02-13 16:27 Kacper Kowalik
2015-10-19 16:29 Justin Lecher

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=1668107003.a9c88b65ca1f9b2a251ee542040570f361ba0b6a.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