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/pytest-django/
Date: Fri, 20 Nov 2020 14:14:13 +0000 (UTC)	[thread overview]
Message-ID: <1605881649.31c199cdd499100b4c790ed8c6a8763fcb0ac640.sam@gentoo> (raw)

commit:     31c199cdd499100b4c790ed8c6a8763fcb0ac640
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Nov 20 14:09:40 2020 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Nov 20 14:14:09 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=31c199cd

dev-python/pytest-django: ppc keyworded (bug #752396)

Package-Manager: Portage-3.0.9, Repoman-3.0.2
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-python/pytest-django/pytest-django-4.1.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/pytest-django/pytest-django-4.1.0.ebuild b/dev-python/pytest-django/pytest-django-4.1.0.ebuild
index 65b147eeccb..b51de52635e 100644
--- a/dev-python/pytest-django/pytest-django-4.1.0.ebuild
+++ b/dev-python/pytest-django/pytest-django-4.1.0.ebuild
@@ -17,7 +17,7 @@ SRC_URI="
 		-> ${P}.gh.tar.gz"
 
 LICENSE="BSD"
-KEYWORDS="~amd64 ~arm ~arm64 ~ppc64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux"
 SLOT="0"
 
 RDEPEND="


             reply	other threads:[~2020-11-20 14:14 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 14:14 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-12 15:05 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-django/ Sam James
2024-09-21 10:43 Michał Górny
2024-09-21  9:59 Sam James
2024-09-03  5:23 Michał Górny
2024-08-29  6:34 Jakov Smolić
2024-08-29  6:34 Jakov Smolić
2024-06-19 17:21 Michał Górny
2024-06-19 17:21 Michał Górny
2024-04-19  6:39 Ionen Wolkens
2024-04-18 16:17 Arthur Zamarin
2024-03-09 16:55 Andrew Ammerlaan
2024-02-14 12:36 Michał Górny
2024-02-14 12:26 Michał Górny
2024-01-30 14:19 Michał Górny
2023-11-29 10:20 Michał Górny
2023-11-08 15:39 Michał Górny
2023-10-30 18:10 Michał Górny
2023-08-24 12:47 Michał Górny
2023-08-24 12:40 Sam James
2023-07-23 21:44 Sam James
2023-07-23 14:47 Michał Górny
2023-07-23 14:47 Michał Górny
2022-01-01 18:48 Michał Górny
2022-01-01 18:11 Arthur Zamarin
2021-12-07 23:27 Michał Górny
2021-12-02 23:13 Michał Górny
2021-12-01 19:14 Michał Górny
2021-07-16 21:53 Michał Górny
2021-07-16 21:44 Sam James
2021-07-14  6:22 Agostino Sarubbo
2021-07-13 20:05 Sam James
2021-07-13  6:26 Agostino Sarubbo
2021-06-26  2:52 Sam James
2021-06-24  8:20 Michał Górny
2021-06-24  4:26 Agostino Sarubbo
2021-06-22 18:25 Marek Szuba
2021-06-14  6:39 Sergei Trofimovich
2021-06-14  6:37 Sergei Trofimovich
2021-06-09 14:43 Sergei Trofimovich
2021-06-08 11:42 Michał Górny
2021-05-19  6:02 Michał Górny
2021-05-18 23:20 Sam James
2021-05-15 21:18 Michał Górny
2021-04-11 10:47 Michał Górny
2021-01-18 14:52 Sam James
2020-12-21 22:16 Sam James
2020-12-21 22:16 Sam James
2020-11-27 16:18 Michał Górny
2020-11-20 14:14 Sam James
2020-11-07  1:23 Sam James
2020-11-02 10:34 Michał Górny
2020-10-22 21:06 Michał Górny
2020-10-16 15:44 Michał Górny
2020-10-07  7:28 Michał Górny
2020-09-21 16:06 Michał Górny
2020-08-29  6:13 Michał Górny
2020-07-11  7:04 Michał Górny
2020-07-11  7:04 Michał Górny
2020-07-09  8:59 Agostino Sarubbo
2020-04-28 13:12 Agostino Sarubbo
2020-04-04 17:04 Michał Górny
2020-03-28 18:49 Michał Górny
2020-03-08 14:29 Michał Górny
2020-02-05 20:11 Michał Górny
2018-11-17 19:48 Virgil Dupras
2017-05-29 16:33 Pacho Ramos
2017-05-02 15:15 Michał Górny
2017-01-12 19:19 Justin Lecher
2015-11-09 11:49 Justin Lecher
2015-09-02  7:21 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=1605881649.31c199cdd499100b4c790ed8c6a8763fcb0ac640.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