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-forked/
Date: Wed, 25 Mar 2020 15:27:18 +0000 (UTC)	[thread overview]
Message-ID: <1585150015.1ccd13c941a3fe460fe30589eba22ea41f79f943.ago@gentoo> (raw)

commit:     1ccd13c941a3fe460fe30589eba22ea41f79f943
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 25 15:26:55 2020 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Wed Mar 25 15:26:55 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1ccd13c9

dev-python/pytest-forked: ia64 stable wrt bug #714456

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

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

diff --git a/dev-python/pytest-forked/pytest-forked-1.1.3.ebuild b/dev-python/pytest-forked/pytest-forked-1.1.3.ebuild
index 57d5565144e..30021563c47 100644
--- a/dev-python/pytest-forked/pytest-forked-1.1.3.ebuild
+++ b/dev-python/pytest-forked/pytest-forked-1.1.3.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 SLOT="0"
 LICENSE="MIT"
-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="test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2020-03-25 15:27 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 15:27 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-10 17:01 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-forked/ Michał Górny
2024-06-10 17:01 Michał Górny
2024-02-07  9:14 Michał Górny
2023-05-24  7:02 Michał Górny
2023-04-05  8:17 Michał Górny
2023-04-05  7:21 Arthur Zamarin
2023-02-13  6:05 Michał Górny
2022-06-10  4:15 Michał Górny
2022-06-10  3:09 Sam James
2022-05-09 20:38 Michał Górny
2022-05-09 20:12 Michał Górny
2022-01-10 19:50 Michał Górny
2022-01-10 19:45 Arthur Zamarin
2021-12-10 17:12 Arthur Zamarin
2021-05-05 17:05 Michał Górny
2020-09-21 16:06 Michał Górny
2020-09-20  7:57 Michał Górny
2020-09-18 15:43 Michał Górny
2020-09-09  0:37 Sam James
2020-07-30 20:46 Michał Górny
2020-07-28 15:51 Sam James
2020-07-28 15:47 Sam James
2020-07-28 12:48 Michał Górny
2020-07-23 10:00 Michał Górny
2020-06-25 18:52 Michał Górny
2020-05-26 12:58 Michał Górny
2020-05-04 11:44 Michał Górny
2020-03-28 18:49 Michał Górny
2020-03-28 18:49 Michał Górny
2020-03-28 18:49 Michał Górny
2019-11-23 10:35 Michał Górny
2019-11-23 10:35 Michał Górny
2019-04-12  3:52 Aaron Bauman
2018-12-28 20:44 Mikle Kolyada
2018-11-11 10:11 Mikle Kolyada
2018-11-08 23:35 Sergei Trofimovich
2018-10-31 23:35 Sergei Trofimovich
2018-10-17 18:38 Sergei Trofimovich
2018-10-14  8:04 Mikle Kolyada
2018-10-13  6:56 Tobias Klausmann
2018-10-09 21:24 Thomas Deutschmann
2018-10-09  5:12 Matt Turner
2018-10-09  5:12 Matt Turner
2018-08-17  1:38 Mikle Kolyada
2018-07-16 19:57 Michał Górny
2018-02-17 21:51 Patrice Clement
2017-08-22  3:42 Tim Harder

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=1585150015.1ccd13c941a3fe460fe30589eba22ea41f79f943.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