public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/python-dateutil/
Date: Sun,  1 Jul 2018 15:19:38 +0000 (UTC)	[thread overview]
Message-ID: <1530458354.a2e9bbc12213a09aeeb2a4b1315996653f5fc102.pacho@gentoo> (raw)

commit:     a2e9bbc12213a09aeeb2a4b1315996653f5fc102
Author:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Sun Jul  1 15:04:28 2018 +0000
Commit:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Sun Jul  1 15:19:14 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a2e9bbc1

dev-python/python-dateutil: amd64 stable, bug #659662

Package-Manager: Portage-2.3.41, Repoman-2.3.9

 dev-python/python-dateutil/python-dateutil-2.7.2-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/python-dateutil/python-dateutil-2.7.2-r1.ebuild b/dev-python/python-dateutil/python-dateutil-2.7.2-r1.ebuild
index 9f6ff3e2176..384f251e2de 100644
--- a/dev-python/python-dateutil/python-dateutil-2.7.2-r1.ebuild
+++ b/dev-python/python-dateutil/python-dateutil-2.7.2-r1.ebuild
@@ -17,7 +17,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh sparc ~x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos"
+KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh sparc ~x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos"
 IUSE="test"
 
 RDEPEND="


             reply	other threads:[~2018-07-01 15:19 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-01 15:19 Pacho Ramos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-14 12:42 [gentoo-commits] repo/gentoo:master commit in: dev-python/python-dateutil/ Michał Górny
2024-05-09 17:32 Michał Górny
2024-03-16  9:31 Arthur Zamarin
2024-03-02  6:43 Michał Górny
2023-05-25 14:38 Michał Górny
2022-06-13  8:23 Michał Górny
2022-05-11 14:05 Michał Górny
2022-05-11 14:05 Michał Górny
2021-08-16  5:13 Agostino Sarubbo
2021-08-15  7:42 Michał Górny
2021-07-03  8:16 Michał Górny
2021-05-07 22:22 Michał Górny
2020-09-20 10:24 Michał Górny
2020-05-26  9:26 Michał Górny
2020-02-12 16:14 Agostino Sarubbo
2020-01-27 11:31 Mikle Kolyada
2020-01-26 11:32 Sergei Trofimovich
2020-01-23 12:18 Agostino Sarubbo
2020-01-23 10:59 Agostino Sarubbo
2020-01-23 10:56 Agostino Sarubbo
2020-01-23 10:52 Agostino Sarubbo
2020-01-23 10:40 Agostino Sarubbo
2020-01-23 10:36 Agostino Sarubbo
2020-01-22 19:44 Michał Górny
2020-01-22 19:44 Michał Górny
2019-11-26  0:10 Patrick McLean
2019-11-19 15:40 Agostino Sarubbo
2019-11-18 12:03 Agostino Sarubbo
2019-10-17 22:30 Aaron W. Swenson
2018-10-27 19:20 Sebastian Pipping
2018-10-25 21:16 Sebastian Pipping
2018-09-16 20:25 Matt Turner
2018-09-16 20:25 Matt Turner
2018-08-20  5:01 Mikle Kolyada
2018-08-18 10:29 Michał Górny
2018-07-31  0:28 Mikle Kolyada
2018-07-20 15:53 Tobias Klausmann
2018-07-07  9:02 Sergei Trofimovich
2018-07-04 18:44 Sergei Trofimovich
2018-07-02  0:49 Thomas Deutschmann
2018-07-01  8:51 Sergei Trofimovich
2018-06-30 18:45 Mart Raudsepp
2018-05-07  0:12 Mart Raudsepp
2018-03-27 20:38 Tim Harder
2018-03-24 22:37 Tim Harder
2018-02-21 17:20 Michał Górny
2017-08-27  8:07 Tim Harder
2017-06-15 18:19 Markus Meier
2017-05-22 16:48 Tobias Klausmann
2017-05-22 11:40 Agostino Sarubbo
2017-05-19 21:44 Michael Weber
2017-05-06 11:13 Jeroen Roovers
2017-05-03  9:26 Michał Górny
2017-02-13  8:04 Zac Medico
2016-11-30 13:54 Lars Wendler
2016-05-11 20:33 Mike Gilbert
2016-03-15  3:25 Tim Harder
2015-10-19 16:29 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=1530458354.a2e9bbc12213a09aeeb2a4b1315996653f5fc102.pacho@gentoo \
    --to=pacho@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