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/rope/
Date: Thu,  6 May 2021 21:19:53 +0000 (UTC)	[thread overview]
Message-ID: <1620335989.783507ef9e41fad01a820796568d83e6f0420e9c.sam@gentoo> (raw)

commit:     783507ef9e41fad01a820796568d83e6f0420e9c
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu May  6 21:19:49 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu May  6 21:19:49 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=783507ef

dev-python/rope: Stabilize 0.18.0-r1 ALLARCHES, #788541

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

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

diff --git a/dev-python/rope/rope-0.18.0-r1.ebuild b/dev-python/rope/rope-0.18.0-r1.ebuild
index 30b91ee55c4..f3463196ae8 100644
--- a/dev-python/rope/rope-0.18.0-r1.ebuild
+++ b/dev-python/rope/rope-0.18.0-r1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="LGPL-3"
 SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~arm64 x86 ~amd64-linux ~x86-linux"
 
 IUSE="doc"
 


             reply	other threads:[~2021-05-06 21:19 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 21:19 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-11 19:04 [gentoo-commits] repo/gentoo:master commit in: dev-python/rope/ Michał Górny
2024-04-11 17:41 Arthur Zamarin
2024-03-24 18:17 Michał Górny
2024-03-24 16:22 Michał Górny
2024-02-03 20:03 Michał Górny
2024-02-03 19:09 Sam James
2024-01-18 17:15 Arthur Zamarin
2023-11-29 11:04 Michał Górny
2023-11-24 23:14 Sam James
2023-11-06  6:22 Michał Górny
2023-11-02  5:44 Michał Górny
2023-11-02  4:12 Sam James
2023-09-28  4:43 Michał Górny
2023-08-03  4:39 Michał Górny
2023-08-02 19:25 Arthur Zamarin
2023-06-30  2:56 Michał Górny
2023-06-06  5:57 Michał Górny
2023-06-06  1:51 Sam James
2023-05-05 17:30 Arthur Zamarin
2023-03-16  4:07 Michał Górny
2023-02-28 19:09 Sam James
2023-02-17  6:21 Michał Górny
2023-02-16 22:50 Sam James
2023-01-17  5:08 Michał Górny
2022-12-31 12:37 Michał Górny
2022-12-31 12:12 Sam James
2022-12-16 11:32 Michał Górny
2022-11-30  3:09 Michał Górny
2022-11-30  0:52 Sam James
2022-11-29 21:46 Jakov Smolić
2022-11-26  6:28 Michał Górny
2022-11-23  8:41 Michał Górny
2022-10-22  6:22 Michał Górny
2022-08-31 18:19 Arthur Zamarin
2022-08-30 18:53 Michał Górny
2022-08-30 17:08 Jakov Smolić
2022-07-30 12:35 Arthur Zamarin
2022-07-30  2:33 Sam James
2022-06-27  9:29 Michał Górny
2022-06-27  7:34 Agostino Sarubbo
2022-06-24 20:45 Jakov Smolić
2022-06-22 17:31 Arthur Zamarin
2022-05-26  8:07 Michał Górny
2022-05-15 10:41 Michał Górny
2022-05-15 10:41 Michał Górny
2022-05-15  8:19 Jakov Smolić
2022-04-08  8:56 Michał Górny
2022-03-31 14:08 Michał Górny
2022-03-31 13:55 Jakov Smolić
2022-02-27  8:49 Michał Górny
2022-02-26  8:34 Michał Górny
2021-12-23 22:46 Michał Górny
2021-12-23 22:39 Sam James
2021-11-22 23:04 Michał Górny
2021-11-21 20:14 Michał Górny
2021-11-21 19:28 Jakov Smolić
2021-10-24  8:43 Michał Górny
2021-10-18 20:40 Michał Górny
2021-09-18 21:38 Michał Górny
2021-09-18  7:00 Michał Górny
2021-09-09 14:12 Andrew Ammerlaan
2021-05-26  6:49 Agostino Sarubbo
2021-05-06 23:03 Michał Górny
2021-04-19  6:56 Michał Górny
2020-12-16 17:25 Michał Górny
2020-12-16 16:46 Sam James
2020-12-05  9:58 Michał Górny
2020-11-05  1:39 Matt Turner
2020-11-05  1:39 Matt Turner
2020-10-13 18:06 Sam James
2020-07-17  4:14 Matt Turner
2020-03-29  7:31 Michał Górny
2020-02-15 20:43 Matt Turner
2017-11-02 12:29 Michał Górny
2017-11-02 12:29 Michał Górny
2017-09-14  2:00 Tim Harder
2017-03-10 17:24 Patrick Lauer
2016-08-22  8:56 Patrice Clement
2016-08-22  8:56 Patrice Clement

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=1620335989.783507ef9e41fad01a820796568d83e6f0420e9c.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