public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/debugpy/
Date: Sat, 11 Sep 2021 13:12:57 +0000 (UTC)	[thread overview]
Message-ID: <1631364409.af645f658afec434ff2e318c3925b1a71e681477.dlan@gentoo> (raw)

commit:     af645f658afec434ff2e318c3925b1a71e681477
Author:     Yixun Lan <dlan <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 11 12:46:49 2021 +0000
Commit:     Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Sat Sep 11 12:46:49 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=af645f65

dev-python/debugpy: keyword ~riscv

Package-Manager: Portage-3.0.22, Repoman-3.0.3
Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>

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

diff --git a/dev-python/debugpy/debugpy-1.4.2.ebuild b/dev-python/debugpy/debugpy-1.4.2.ebuild
index 814441d2e40..4569bdc92ac 100644
--- a/dev-python/debugpy/debugpy-1.4.2.ebuild
+++ b/dev-python/debugpy/debugpy-1.4.2.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://github.com/microsoft/${PN}/archive/refs/tags/v${PV}.tar.gz -> $
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~amd64"
+KEYWORDS="~amd64 ~riscv"
 
 # There is not enough time in the universe for this test suite
 RESTRICT="test"


             reply	other threads:[~2021-09-11 13:13 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-11 13:12 Yixun Lan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-09 18:10 [gentoo-commits] repo/gentoo:master commit in: dev-python/debugpy/ Michał Górny
2023-12-02 15:01 Arthur Zamarin
2023-12-02  9:27 Arthur Zamarin
2023-11-25  8:51 Sam James
2023-10-24 14:42 Michał Górny
2023-03-11  9:43 Arthur Zamarin
2023-03-11  8:34 Arthur Zamarin
2023-03-11  8:34 Arthur Zamarin
2023-03-11  8:34 Arthur Zamarin
2023-03-11  8:10 Arthur Zamarin
2023-03-11  8:06 Arthur Zamarin
2023-03-11  8:06 Arthur Zamarin
2023-03-11  8:04 Arthur Zamarin
2023-02-02 16:37 Andrew Ammerlaan
2022-09-22  7:45 Michał Górny
2022-09-20  8:08 Michał Górny
2022-09-20  7:43 Jakov Smolić
2022-09-19 20:14 Jakov Smolić
2022-09-19 20:10 Jakov Smolić
2022-09-19 19:26 Arthur Zamarin
2022-09-19 19:26 Arthur Zamarin
2022-09-19 19:25 Arthur Zamarin
2022-09-19 19:24 Arthur Zamarin
2022-09-19 19:23 Arthur Zamarin
2022-08-16 18:51 Arthur Zamarin
2022-08-12 10:49 Agostino Sarubbo
2022-08-10  8:04 Arthur Zamarin
2022-08-10  8:04 Arthur Zamarin
2022-08-09  7:43 Agostino Sarubbo
2022-08-09  4:00 Arthur Zamarin
2022-08-09  4:00 Arthur Zamarin
2022-08-08 19:50 Arthur Zamarin
2022-08-08 19:41 Arthur Zamarin
2022-07-15  7:25 Agostino Sarubbo
2022-07-15  7:21 Agostino Sarubbo
2022-07-15  6:00 Arthur Zamarin
2022-07-14 20:44 Arthur Zamarin
2022-07-14 20:23 Arthur Zamarin
2022-07-14 20:08 Arthur Zamarin
2022-07-14 19:41 Arthur Zamarin
2022-07-14 19:14 Arthur Zamarin
2022-07-08  7:40 Arthur Zamarin
2022-05-25  9:07 Andrew Ammerlaan
2022-02-14  8:35 Matt Turner
2022-01-30 13:32 James Le Cuirot
2021-11-20  3:54 Sam James
2021-11-19 19:24 Arthur Zamarin
2021-11-19 11:58 Sam James
2021-11-19  9:07 Sam James
2021-11-19  8:34 Sam James
2021-11-19  7:30 Sam James
2021-11-17  7:55 Sam James
2021-11-15  6:02 Sam James
2021-11-14  8:46 Michał Górny
2021-11-11  8:36 Jakov Smolić
2021-11-05 14:57 Jakov Smolić
2021-11-05  2:20 Sam James
2021-10-19  7:22 Michał Górny
2021-10-17  7:41 Michał Górny
2021-10-13 19:02 Arthur Zamarin
2021-10-10 23:45 Sam James
2021-09-12 17:38 Sam James
2021-09-12 17:38 Sam James
2021-09-12  8:22 Sam James
2021-09-12  8:21 Sam James
2021-09-12  8:16 Andrew Ammerlaan
2021-09-11 15:59 Sam James
2021-09-10 13:41 Andrew Ammerlaan
2021-09-08  1:25 Sam James
2021-09-07  2:47 Sam James
2021-09-06 21:26 Sam James
2021-08-27 21:21 Yixun Lan
2021-08-26 20:36 Sam James
2021-08-24 18:41 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=1631364409.af645f658afec434ff2e318c3925b1a71e681477.dlan@gentoo \
    --to=dlan@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