public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/nbsphinx/
Date: Sat,  5 Sep 2020 15:25:19 +0000 (UTC)	[thread overview]
Message-ID: <1599319503.f657c93268af98e0121f172ced6a82e52e9bab96.sam@gentoo> (raw)

commit:     f657c93268af98e0121f172ced6a82e52e9bab96
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Sep  5 15:25:03 2020 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Sep  5 15:25:03 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f657c932

dev-python/nbsphinx: Stabilize 0.7.1-r1 ALLARCHES, #740266

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-python/nbsphinx/nbsphinx-0.7.1-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/nbsphinx/nbsphinx-0.7.1-r1.ebuild b/dev-python/nbsphinx/nbsphinx-0.7.1-r1.ebuild
index 1bcfd4e9e45..1ddddad25f0 100644
--- a/dev-python/nbsphinx/nbsphinx-0.7.1-r1.ebuild
+++ b/dev-python/nbsphinx/nbsphinx-0.7.1-r1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~x86"
+KEYWORDS="amd64 ~arm64 x86"
 IUSE=""
 
 RDEPEND="


             reply	other threads:[~2020-09-05 15:25 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05 15:25 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-31  9:21 [gentoo-commits] repo/gentoo:master commit in: dev-python/nbsphinx/ Michał Górny
2024-08-31  8:33 Arthur Zamarin
2024-08-14  6:05 Michał Górny
2024-05-22  9:10 Michał Górny
2024-05-22  9:05 Michał Górny
2024-05-07  1:57 Michał Górny
2024-02-03 10:41 Michał Górny
2023-11-10 13:20 Andrew Ammerlaan
2023-09-30  6:49 Michał Górny
2023-09-30  6:05 Arthur Zamarin
2023-08-28  5:13 Michał Górny
2023-06-27 11:54 Michał Górny
2023-06-27  5:19 Jakov Smolić
2023-05-25  2:55 Michał Górny
2023-04-22 16:24 Michał Górny
2023-04-22 12:46 Sam James
2023-04-14 22:30 Sam James
2023-04-14 21:02 Sam James
2023-04-14 20:43 Sam James
2023-04-14 20:25 Sam James
2023-04-14 20:07 Sam James
2023-03-15  6:52 Michał Górny
2023-03-13  5:12 Michał Górny
2023-03-11  6:37 Yixun Lan
2023-02-17  6:21 Michał Górny
2023-02-16 22:49 Sam James
2023-01-20  4:50 Michał Górny
2022-12-30  7:08 Michał Górny
2022-12-17  7:08 Michał Górny
2022-12-16 21:10 Arthur Zamarin
2022-11-13 18:57 Michał Górny
2022-10-27 10:23 Andrew Ammerlaan
2022-07-10 19:06 Michał Górny
2022-07-10 16:58 Sam James
2022-06-05  9:14 Michał Górny
2022-03-31 19:18 Michał Górny
2022-03-31 17:36 Jakov Smolić
2022-02-26 12:17 Michał Górny
2022-02-04  8:40 Michał Górny
2022-02-04  7:28 Agostino Sarubbo
2022-01-01  1:29 Michał Górny
2021-09-12  7:39 Michał Górny
2021-09-12  7:09 Agostino Sarubbo
2021-08-11  7:06 Michał Górny
2021-07-23 14:08 Andrew Ammerlaan
2021-07-12 22:53 Michał Górny
2021-07-12 21:50 Sam James
2021-06-15  5:40 Michał Górny
2021-06-15  5:25 Sam James
2021-06-03 10:30 Michał Górny
2021-05-19 18:21 Michał Górny
2021-05-19 17:22 Sam James
2021-05-13  8:56 Michał Górny
2021-04-29 19:56 Michał Górny
2021-04-10  8:04 Michał Górny
2021-04-07  8:06 Michał Górny
2021-04-07  6:22 Sam James
2021-02-28 18:20 Michał Górny
2020-09-18 15:30 Michał Górny
2020-09-02  9:12 Michał Górny
2020-08-05 15:10 Michał Górny
2020-07-09 12:40 Michał Górny
2020-07-09 12:40 Michał Górny
2020-06-17  6:56 Michał Górny
2020-06-10  6:42 Michał Górny
2018-12-25 13:57 Benda XU
2018-06-30 19:30 Mart Raudsepp
2018-05-16 15:58 Andreas Sturmlechner
2018-05-16 12:28 Agostino Sarubbo
2018-04-22  1:35 Thomas Deutschmann
2017-06-28  4:02 Sebastien Fabbro
2017-06-27 11:22 Alexis Ballier
2017-03-16 19:13 David Seifert
2017-03-12 12:31 Zac Medico
2016-05-29 14:54 David Seifert
2016-05-29 14:54 David Seifert
2016-05-29 14:54 David Seifert

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=1599319503.f657c93268af98e0121f172ced6a82e52e9bab96.sam@gentoo \
    --to=sam@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