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/bottle/
Date: Mon, 27 Jan 2020 12:44:03 +0000 (UTC)	[thread overview]
Message-ID: <1580129039.3a67ffb511e97d4219fd2a22a3ddf5cd390146cf.ago@gentoo> (raw)

commit:     3a67ffb511e97d4219fd2a22a3ddf5cd390146cf
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 27 12:43:59 2020 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Mon Jan 27 12:43:59 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3a67ffb5

dev-python/bottle: sparc stable wrt bug #706624

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

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

diff --git a/dev-python/bottle/bottle-0.12.18.ebuild b/dev-python/bottle/bottle-0.12.18.ebuild
index a1dbeb5309c..47d789a0553 100644
--- a/dev-python/bottle/bottle-0.12.18.ebuild
+++ b/dev-python/bottle/bottle-0.12.18.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh sparc ~x86"
 IUSE="test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2020-01-27 12:44 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 12:44 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-02  8:59 [gentoo-commits] repo/gentoo:master commit in: dev-python/bottle/ Michał Górny
2024-10-13  3:10 Michał Górny
2024-09-28 12:59 Michał Górny
2024-09-28 12:32 Arthur Zamarin
2024-09-08  2:52 Michał Górny
2024-09-06  9:25 Michał Górny
2024-06-15 13:14 Michał Górny
2024-06-15  8:15 Michał Górny
2023-07-05  8:03 Michał Górny
2023-07-05  5:56 Arthur Zamarin
2023-03-24 19:52 Michał Górny
2023-03-24 19:47 Arthur Zamarin
2023-03-04 18:16 Michał Górny
2023-02-21 19:02 Michał Górny
2022-11-04 18:23 Arthur Zamarin
2022-09-06 18:57 Arthur Zamarin
2022-08-04  7:32 Michał Górny
2022-08-03 17:30 Arthur Zamarin
2022-06-03  6:14 Michał Górny
2022-06-03  5:50 Jakov Smolić
2022-05-27  6:10 Michał Górny
2022-05-26 18:54 Michał Górny
2022-05-14 10:30 WANG Xuerui
2022-05-13  9:08 Michał Górny
2021-07-02 12:26 Marek Szuba
2021-05-07 11:11 Michał Górny
2020-12-16 19:33 Michał Górny
2020-12-16 18:04 Sam James
2020-12-16 11:30 Michał Górny
2020-11-11 20:55 Michał Górny
2020-09-20  8:35 Michał Górny
2020-05-25 19:48 Michał Górny
2020-04-04 14:55 Mart Raudsepp
2020-02-06  7:51 Sergei Trofimovich
2020-01-28  7:41 Agostino Sarubbo
2020-01-27 14:28 Agostino Sarubbo
2020-01-27 14:25 Agostino Sarubbo
2020-01-27 12:51 Agostino Sarubbo
2020-01-27 12:25 Agostino Sarubbo
2020-01-27 11:56 Mikle Kolyada
2020-01-27  7:22 Michał Górny
2020-01-26 16:55 Michał Górny
2019-12-30 10:15 Sergei Trofimovich
2019-12-27 19:54 Sebastian Pipping
2019-12-23  9:36 Mikle Kolyada
2019-12-16 14:38 Michał Górny
2019-12-16 14:38 Michał Górny
2019-12-15 13:53 Agostino Sarubbo
2019-12-15 13:36 Sergei Trofimovich
2019-12-15 13:24 Sergei Trofimovich
2019-12-15 12:44 Agostino Sarubbo
2019-01-01 19:02 Sebastian Pipping
2018-02-21 22:11 Michał Górny
2017-11-01 17:21 Zac Medico
2017-09-30 16:38 Patrick Lauer
2017-01-18 10:11 David Seifert
2017-01-18  9:50 Agostino Sarubbo
2017-01-15 22:10 Tobias Klausmann
2017-01-15 20:35 Jeroen Roovers
2017-01-15 15:50 Agostino Sarubbo
2017-01-15 12:58 Markus Meier
2017-01-11 16:17 Agostino Sarubbo
2017-01-09  0:38 Mike Gilbert
2016-10-22 19:49 Sebastian Pipping
2015-11-20  1:23 Mike Frysinger
2015-10-26 13: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=1580129039.3a67ffb511e97d4219fd2a22a3ddf5cd390146cf.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