public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pytables/
Date: Wed,  2 Jan 2019 19:01:41 +0000 (UTC)	[thread overview]
Message-ID: <1546455692.721db928e0fcd46313c9a3eb09efbfe4f15ba5cd.whissi@gentoo> (raw)

commit:     721db928e0fcd46313c9a3eb09efbfe4f15ba5cd
Author:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Wed Jan  2 19:00:42 2019 +0000
Commit:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Wed Jan  2 19:01:32 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=721db928

dev-python/pytables: x86 stable (bug #673838)

Package-Manager: Portage-2.3.53, Repoman-2.3.12
Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>

 dev-python/pytables/pytables-3.4.4.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-python/pytables/pytables-3.4.4.ebuild b/dev-python/pytables/pytables-3.4.4.ebuild
index 4d78d0413dc..265889bd4b0 100644
--- a/dev-python/pytables/pytables-3.4.4.ebuild
+++ b/dev-python/pytables/pytables-3.4.4.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Authors
+# Copyright 1999-2019 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -16,7 +16,7 @@ HOMEPAGE="https://www.pytables.org/"
 SRC_URI="mirror://pypi/${MY_PN:0:1}/${MY_PN}/${MY_P}.tar.gz"
 
 SLOT="0"
-KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~amd64 x86 ~amd64-linux ~x86-linux"
 LICENSE="BSD"
 IUSE="doc examples test"
 


             reply	other threads:[~2019-01-02 19:01 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 19:01 Thomas Deutschmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-20 17:51 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytables/ Michał Górny
2023-08-20 17:11 Arthur Zamarin
2023-08-20 17:11 Arthur Zamarin
2023-08-20 17:11 Arthur Zamarin
2023-05-20  7:25 Michał Górny
2023-05-04 16:30 Michał Górny
2023-04-29 15:47 Arthur Zamarin
2023-04-29 15:31 Arthur Zamarin
2023-04-29 15:25 Arthur Zamarin
2023-03-25 17:19 Michał Górny
2023-02-20 21:58 Arthur Zamarin
2023-02-20 21:29 Arthur Zamarin
2023-02-13 11:31 Yixun Lan
2023-02-12 20:24 Jakov Smolić
2023-01-06  2:10 Sam James
2022-12-30 17:23 Michał Górny
2022-12-30 17:23 Michał Górny
2022-10-14 13:31 Andrew Ammerlaan
2022-02-02 20:53 Arthur Zamarin
2022-02-02  0:08 Sam James
2022-01-29 10:04 Jakov Smolić
2022-01-29 10:04 Jakov Smolić
2022-01-29  7:22 Arthur Zamarin
2022-01-29  7:01 Arthur Zamarin
2021-12-29  8:30 Michał Górny
2021-12-29  8:30 Michał Górny
2021-12-29  7:58 Sam James
2021-12-29  6:25 Arthur Zamarin
2021-11-20  7:44 Sam James
2021-11-20  6:53 Sam James
2021-11-20  6:35 Sam James
2021-11-19 13:32 Sam James
2021-11-19 13:16 Sam James
2021-11-14 23:51 Sam James
2021-10-24 21:14 Sam James
2021-09-06 23:42 Sam James
2021-09-06 23:37 Sam James
2021-09-06  0:13 Sam James
2021-08-15 22:03 Marek Szuba
2020-10-16 18:22 Michał Górny
2020-08-18  5:52 Sam James
2020-08-18  5:28 Sam James
2020-08-14 23:22 Andreas Sturmlechner
2020-08-07 19:19 Sam James
2020-07-06 14:13 Michał Górny
2020-07-06 11:57 Michał Górny
2020-06-06 22:22 Pacho Ramos
2020-01-30 17:31 Michał Górny
2019-06-15 20:56 Andreas Sturmlechner
2019-01-18 22:20 Craig Andrews
2019-01-17 21:25 Mikle Kolyada
2019-01-01 21:09 Craig Andrews
2018-12-07  0:00 Craig Andrews
2018-12-06 20:47 Craig Andrews
2018-12-06 20:47 Craig Andrews
2017-06-28  4:02 Sebastien Fabbro
2017-06-21 12:11 Agostino Sarubbo
2017-06-19 17:03 Agostino Sarubbo
2017-03-11  0:50 Zac Medico
2016-11-13 18:15 Justin Lecher
2016-11-05 12:34 Justin Lecher
2016-11-05 12:17 Justin Lecher
2015-11-11 17:27 Justin Lecher
2015-09-22  8:10 Justin Lecher
2015-09-04  7:57 Justin Lecher
2015-08-21  9:35 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=1546455692.721db928e0fcd46313c9a3eb09efbfe4f15ba5cd.whissi@gentoo \
    --to=whissi@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