public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/trustme/
Date: Sun, 29 Mar 2020 21:21:53 +0000 (UTC)	[thread overview]
Message-ID: <1585516901.ad10ef387415d4c4178288570630f683aa5aa3a9.slyfox@gentoo> (raw)

commit:     ad10ef387415d4c4178288570630f683aa5aa3a9
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 29 21:14:47 2020 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Mar 29 21:21:41 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ad10ef38

dev-python/trustme: keyworded 0.6.0 for ppc64, bug #711762

Package-Manager: Portage-2.3.96, Repoman-2.3.22
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>

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

diff --git a/dev-python/trustme/trustme-0.6.0.ebuild b/dev-python/trustme/trustme-0.6.0.ebuild
index e58d19dfed3..747f9582143 100644
--- a/dev-python/trustme/trustme-0.6.0.ebuild
+++ b/dev-python/trustme/trustme-0.6.0.ebuild
@@ -12,7 +12,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="|| ( Apache-2.0 MIT )"
 SLOT="0"
-KEYWORDS="~alpha amd64 arm ~arm64 ~ia64 ~sparc x86"
+KEYWORDS="~alpha amd64 arm ~arm64 ~ia64 ~ppc64 ~sparc x86"
 
 RDEPEND="dev-python/cryptography[${PYTHON_USEDEP}]
 	dev-python/idna[${PYTHON_USEDEP}]


             reply	other threads:[~2020-03-29 21:22 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 21:21 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-12  7:44 [gentoo-commits] repo/gentoo:master commit in: dev-python/trustme/ Sam James
2025-02-16 14:46 Michał Górny
2025-01-18 10:03 Michał Górny
2025-01-18  8:56 Arthur Zamarin
2025-01-02  4:54 Michał Górny
2024-10-26 12:48 Arthur Zamarin
2024-10-08  3:00 Michał Górny
2024-07-01  4:35 Arthur Zamarin
2024-05-28 12:10 Michał Górny
2024-05-11 12:06 Michał Górny
2023-08-11 19:12 Michał Górny
2023-08-11 19:08 Arthur Zamarin
2023-07-20 10:16 WANG Xuerui
2023-07-11  5:52 Michał Górny
2023-06-01 17:22 Michał Górny
2023-06-01 17:19 Arthur Zamarin
2023-05-27 15:21 Sam James
2023-05-02  3:14 Michał Górny
2023-05-02  3:14 Michał Górny
2022-07-04  6:57 Michał Górny
2022-06-16  9:23 Michał Górny
2022-06-16  9:06 Jakov Smolić
2022-05-13  9:32 Michał Górny
2022-05-13  9:32 Michał Górny
2022-02-07  9:35 Sam James
2021-11-28 14:42 Michał Górny
2021-09-18 19:43 Michał Górny
2021-09-18 17:18 Sam James
2021-08-13  6:58 Michał Górny
2021-07-31 22:26 Joshua Kinard
2021-07-12 22:43 Michał Górny
2021-07-12 21:50 Sam James
2021-06-08 23:12 Michał Górny
2021-06-01 20:56 Michał Górny
2021-03-15  8:52 Michał Górny
2021-03-15  2:28 Sam James
2021-02-10  8:35 Michał Górny
2020-12-20  9:37 Fabian Groffen
2020-11-28 11:34 Sam James
2020-11-28 11:34 Sam James
2020-09-20 10:47 Michał Górny
2020-07-17 23:25 Sam James
2020-07-17 15:12 Agostino Sarubbo
2020-07-14 16:38 Sergei Trofimovich
2020-07-11 22:08 Sam James
2020-07-09  8:41 Agostino Sarubbo
2020-05-25 19:48 Michał Górny
2020-04-11 12:08 Mart Raudsepp
2020-04-04 10:52 Sergei Trofimovich
2020-03-26 17:17 Michał Górny
2020-03-16  5:54 Matt Turner
2020-03-14 22:11 Sergei Trofimovich
2020-03-14 18:20 Mikle Kolyada
2020-03-11  7:21 Sergei Trofimovich
2019-12-20 20:10 Michał Górny
2019-11-22 11:44 Michał Górny
2019-11-22 11:44 Michał Górny
2019-09-07  6:37 Michał Górny
2019-09-07  6:37 Michał Górny
2019-09-07  6:37 Michał Górny
2019-07-31 14:32 Mikle Kolyada
2019-07-31 14:32 Mikle Kolyada
2019-07-29 10:48 Mikle Kolyada
2019-07-22 14:12 Aaron Bauman
2019-07-14 12:27 Michał Górny
2019-03-09  1:12 William Hubbs
2019-03-08 17:55 William Hubbs

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=1585516901.ad10ef387415d4c4178288570630f683aa5aa3a9.slyfox@gentoo \
    --to=slyfox@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