public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Aaron Bauman" <bman@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/python-futures/
Date: Fri, 12 Apr 2019 05:10:51 +0000 (UTC)	[thread overview]
Message-ID: <1555045843.03d231ef0ec7a31d3857a46bcab5b7b486a4e0a1.bman@gentoo> (raw)

commit:     03d231ef0ec7a31d3857a46bcab5b7b486a4e0a1
Author:     Aaron Bauman <bman <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 12 05:09:43 2019 +0000
Commit:     Aaron Bauman <bman <AT> gentoo <DOT> org>
CommitDate: Fri Apr 12 05:10:43 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=03d231ef

virtual/python-futures: arm64 stable (bug #676562)

Signed-off-by: Aaron Bauman <bman <AT> gentoo.org>
Package-Manager: Portage-2.3.62, Repoman-2.3.11

 virtual/python-futures/python-futures-1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/virtual/python-futures/python-futures-1.ebuild b/virtual/python-futures/python-futures-1.ebuild
index 984dd4b58db..7164f389204 100644
--- a/virtual/python-futures/python-futures-1.ebuild
+++ b/virtual/python-futures/python-futures-1.ebuild
@@ -9,7 +9,7 @@ inherit python-r1
 
 DESCRIPTION="A virtual for the Python concurrent.futures module"
 SLOT="0"
-KEYWORDS="alpha amd64 arm ~arm64 hppa ia64 m68k ppc ppc64 s390 sh sparc x86 ~amd64-fbsd ~amd64-linux"
+KEYWORDS="alpha amd64 arm arm64 hppa ia64 m68k ppc ppc64 s390 sh sparc x86 ~amd64-fbsd ~amd64-linux"
 REQUIRED_USE="${PYTHON_REQUIRED_USE}"
 
 RDEPEND="${PYTHON_DEPS}


             reply	other threads:[~2019-04-12  5:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12  5:10 Aaron Bauman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-04 12:34 [gentoo-commits] repo/gentoo:master commit in: virtual/python-futures/ Michał Górny
2019-11-15  7:33 Michał Górny
2019-06-25 12:09 Michael Haubenwallner
2019-03-03 12:17 Mikle Kolyada
2019-03-03 12:17 Mikle Kolyada
2019-03-03 12:17 Mikle Kolyada
2019-03-02 23:21 Matt Turner
2019-02-25 22:23 Sergei Trofimovich
2019-02-19 21:15 Markus Meier
2019-02-12 21:03 Sergei Trofimovich
2019-02-10  7:24 Mikle Kolyada
2019-02-09 18:36 Thomas Deutschmann
2019-02-02 20:44 Sergei Trofimovich
2019-02-01 14:55 Tobias Klausmann
2019-01-30  8:13 Sergei Trofimovich
2019-01-27 19:00 Virgil Dupras
2018-02-21 22:11 Michał Górny
2018-02-02  9:05 Fabian Groffen
2017-05-19 13:37 Michael Weber
2017-04-21  7:33 David Seifert
2017-01-26 22:35 Michał Górny
2016-02-28  7:00 Matt Thode
2016-01-11  9:56 Agostino Sarubbo
2016-01-10 11:22 Agostino Sarubbo
2015-12-26 12:03 Agostino Sarubbo
2015-11-26 19:25 Markus Meier
2015-11-24  9:37 Jeroen Roovers
2015-11-22  5:38 Jeroen Roovers
2015-11-18 15:40 Justin Lecher
2015-11-10 11:49 Justin Lecher
2015-11-10 10:54 Justin Lecher
2015-11-10 10:54 Justin Lecher
2015-11-10 10:54 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=1555045843.03d231ef0ec7a31d3857a46bcab5b7b486a4e0a1.bman@gentoo \
    --to=bman@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