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-expect/
Date: Thu,  4 Jun 2020 06:35:53 +0000 (UTC)	[thread overview]
Message-ID: <1591252546.e8cf1006c277ed62b3597aaff868dc96c8aecb2a.ago@gentoo> (raw)

commit:     e8cf1006c277ed62b3597aaff868dc96c8aecb2a
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Thu Jun  4 06:34:35 2020 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Thu Jun  4 06:35:46 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e8cf1006

dev-python/pytest-expect: x86 stable wrt bug #726552

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

 dev-python/pytest-expect/pytest-expect-1.1.0-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/pytest-expect/pytest-expect-1.1.0-r1.ebuild b/dev-python/pytest-expect/pytest-expect-1.1.0-r1.ebuild
index d3bc647ff3c..f223507f9a9 100644
--- a/dev-python/pytest-expect/pytest-expect-1.1.0-r1.ebuild
+++ b/dev-python/pytest-expect/pytest-expect-1.1.0-r1.ebuild
@@ -12,7 +12,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~mips ppc ppc64 ~s390 sparc ~x86"
+KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~mips ppc ppc64 ~s390 sparc x86"
 IUSE=""
 
 RDEPEND="


             reply	other threads:[~2020-06-04  6:36 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04  6:35 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-09 19:13 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-expect/ Michał Górny
2023-05-24  8:36 Sam James
2023-03-17 15:23 Michał Górny
2022-06-13  8:20 Michał Górny
2022-06-12  5:51 Michał Górny
2022-05-11 17:54 Michał Górny
2022-05-11 17:54 Michał Górny
2021-09-25 21:27 James Le Cuirot
2021-05-07 11:58 Michał Górny
2021-05-07 11:58 Michał Górny
2020-08-01 10:09 Michał Górny
2020-07-19 18:33 Michał Górny
2020-07-14 16:32 Sam James
2020-06-10  8:11 Michał Górny
2020-06-06 19:31 Mart Raudsepp
2020-06-05 16:10 Sergei Trofimovich
2020-06-04  6:23 Agostino Sarubbo
2020-06-03 15:17 Agostino Sarubbo
2020-06-03 15:12 Agostino Sarubbo
2020-06-01 20:51 Sergei Trofimovich
2020-06-01 19:52 Sergei Trofimovich
2020-05-26 16:23 Michał Górny
2019-11-27  1:13 Patrick McLean
2019-11-02  8:19 Mikle Kolyada
2019-01-05 17:19 Mikle Kolyada
2018-07-22  2:14 Mikle Kolyada
2018-07-20 15:53 Tobias Klausmann
2018-07-15 10:25 Sergei Trofimovich
2018-07-14 20:10 Sergei Trofimovich
2018-07-02 21:24 Sergei Trofimovich
2018-07-01 15:19 Pacho Ramos
2018-06-30 17:55 Sergei Trofimovich
2018-02-17 21:51 Patrice Clement
2017-12-20 21:53 Sergei Trofimovich
2017-11-23 22:31 Matt Turner
2017-09-22 19:40 Sergei Trofimovich
2017-08-20  2:17 Tim Harder
2017-07-01 11:19 Sergei Trofimovich
2017-05-26 20:56 Mart Raudsepp
2017-05-26 18:36 Markus Meier
2017-05-23 20:00 Michael Weber
2017-05-18 20:00 Michael Weber
2017-05-17 19:22 Markus Meier
2017-05-10 20:10 Jeroen Roovers
2017-05-09  1:41 Zac Medico

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=1591252546.e8cf1006c277ed62b3597aaff868dc96c8aecb2a.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