public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/incremental/
Date: Wed, 13 Dec 2017 22:15:44 +0000 (UTC)	[thread overview]
Message-ID: <1513203337.589ad4d526e64272a68762ae91eaeebc7b965fb1.slyfox@gentoo> (raw)

commit:     589ad4d526e64272a68762ae91eaeebc7b965fb1
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Wed Dec 13 22:13:25 2017 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Wed Dec 13 22:15:37 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=589ad4d5

dev-python/incremental: keyworded 16.10.1 for sparc, bug #605122 (thanks to Rolf Eike Beer)

Package-Manager: Portage-2.3.16, Repoman-2.3.6
RepoMan-Options: --include-arches="sparc"

 dev-python/incremental/incremental-16.10.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/incremental/incremental-16.10.1.ebuild b/dev-python/incremental/incremental-16.10.1.ebuild
index 0d30bfab5bf..31500c7670a 100644
--- a/dev-python/incremental/incremental-16.10.1.ebuild
+++ b/dev-python/incremental/incremental-16.10.1.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 x86"
+KEYWORDS="alpha amd64 arm ~arm64 ~hppa ia64 ~mips ppc ppc64 ~sparc x86"
 IUSE=""
 
 RDEPEND=""


             reply	other threads:[~2017-12-13 22:15 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 22:15 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-17  7:58 [gentoo-commits] repo/gentoo:master commit in: dev-python/incremental/ Michał Górny
2024-08-17  7:51 Michał Górny
2024-07-30 13:48 Michał Górny
2024-06-28  7:47 Petr Vaněk
2023-07-05  8:03 Michał Górny
2023-07-05  5:56 Arthur Zamarin
2023-05-29  9:31 Michał Górny
2023-05-28 18:11 Sam James
2022-11-19  8:44 Arthur Zamarin
2022-11-19  8:36 Arthur Zamarin
2022-10-16  5:41 Arthur Zamarin
2022-05-13  9:08 Michał Górny
2022-03-15 14:10 Michał Górny
2022-03-15 11:36 Jakov Smolić
2022-02-02  9:27 Michał Górny
2022-02-02  9:27 Michał Górny
2022-01-27 22:56 James Le Cuirot
2021-06-12 10:18 Michał Górny
2021-06-11 21:09 Michał Górny
2021-05-13 22:10 Michał Górny
2021-04-05 18:39 Michał Górny
2021-03-02  8:21 Michał Górny
2020-11-28 11:39 Sam James
2020-11-28 11:39 Sam James
2020-09-30 22:50 Louis Sautier
2020-08-04 12:01 Michał Górny
2020-07-04  9:07 Michał Górny
2020-05-27  9:18 Michał Górny
2020-05-04 11:07 Michał Górny
2020-01-22 23:40 Thomas Deutschmann
2019-12-29  9:11 Mikle Kolyada
2019-12-19 18:35 Sergei Trofimovich
2019-12-15 13:59 Agostino Sarubbo
2019-12-15 13:53 Agostino Sarubbo
2019-12-15 13:36 Sergei Trofimovich
2019-12-15 11:38 Agostino Sarubbo
2019-12-02  2:48 Aaron Bauman
2019-06-25 12:09 Michael Haubenwallner
2019-03-20 10:31 Fabian Groffen
2019-01-17 20:45 Mikle Kolyada
2018-12-31 10:21 Mikle Kolyada
2018-08-20 18:17 Sergei Trofimovich
2018-05-04 13:05 Mart Raudsepp
2018-03-30 18:08 Sergei Trofimovich
2018-02-21 22:11 Michał Górny
2017-12-13 22:15 Sergei Trofimovich
2017-10-28 22:34 Sergei Trofimovich
2017-10-08 11:00 Michał Górny
2017-10-05  4:36 Markus Meier
2017-09-28 13:42 Michael Palimaka
2017-07-02 15:02 Sergei Trofimovich
2017-07-02 15:02 Sergei Trofimovich
2017-06-28 13:19 Agostino Sarubbo
2017-06-26 20:18 Tobias Klausmann
2017-06-09 18:18 Brian Dolbec
2017-06-09 14:19 Brian Dolbec
2017-05-26 10:16 Tobias Klausmann
2017-03-30  2:40 Brian Dolbec
2017-03-29  1:43 Brian Dolbec
2017-01-16 18:30 Brian Dolbec
2016-12-24 21:54 Brian Dolbec

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=1513203337.589ad4d526e64272a68762ae91eaeebc7b965fb1.slyfox@gentoo \
    --to=slyfox@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