public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-check/
Date: Mon, 15 Nov 2021 16:29:29 +0000 (UTC)	[thread overview]
Message-ID: <1636993651.207b9097bd8229441be73bea3e1239e10a0bbfcc.ago@gentoo> (raw)

commit:     207b9097bd8229441be73bea3e1239e10a0bbfcc
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 15 16:27:31 2021 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Mon Nov 15 16:27:31 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=207b9097

dev-python/pytest-check: ppc stable wrt bug #803719

Package-Manager: Portage-3.0.20, Repoman-3.0.3
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

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

diff --git a/dev-python/pytest-check/pytest-check-1.0.4.ebuild b/dev-python/pytest-check/pytest-check-1.0.4.ebuild
index aaa88442e40e..7065a227d003 100644
--- a/dev-python/pytest-check/pytest-check-1.0.4.ebuild
+++ b/dev-python/pytest-check/pytest-check-1.0.4.ebuild
@@ -16,7 +16,7 @@ SRC_URI="
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~ppc ~ppc64 sparc x86"
+KEYWORDS="amd64 ~arm ~arm64 ppc ~ppc64 sparc x86"
 
 RDEPEND=">=dev-python/pytest-6[${PYTHON_USEDEP}]"
 BDEPEND="dev-python/flit_core[${PYTHON_USEDEP}]"


             reply	other threads:[~2021-11-15 16:29 UTC|newest]

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

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=1636993651.207b9097bd8229441be73bea3e1239e10a0bbfcc.ago@gentoo \
    --to=ago@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