public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-arch/snappy/
Date: Sat, 17 Mar 2018 11:33:52 +0000 (UTC)	[thread overview]
Message-ID: <1521286431.df1ed35261f25548fcc9bfe2f09eef43846175ec.jer@gentoo> (raw)

commit:     df1ed35261f25548fcc9bfe2f09eef43846175ec
Author:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 17 11:32:32 2018 +0000
Commit:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Sat Mar 17 11:33:51 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=df1ed352

app-arch/snappy: Mark ~sparc too.

Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --ignore-arches

 app-arch/snappy/snappy-1.1.7.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-arch/snappy/snappy-1.1.7.ebuild b/app-arch/snappy/snappy-1.1.7.ebuild
index 36c15e2a3d9..0971da8ddfb 100644
--- a/app-arch/snappy/snappy-1.1.7.ebuild
+++ b/app-arch/snappy/snappy-1.1.7.ebuild
@@ -10,7 +10,7 @@ SRC_URI="https://github.com/google/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
 
 LICENSE="BSD"
 SLOT="0/${PV%%.*}"
-KEYWORDS="alpha amd64 ~arm ~arm64 hppa ia64 ppc ppc64 x86 ~amd64-fbsd ~amd64-linux ~x86-linux"
+KEYWORDS="alpha amd64 ~arm ~arm64 hppa ia64 ppc ppc64 ~sparc x86 ~amd64-fbsd ~amd64-linux ~x86-linux"
 IUSE="static-libs test"
 # upstream killed static lib support with build system update
 # (and we have packages depending on the flag)


             reply	other threads:[~2018-03-17 11:33 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-17 11:33 Jeroen Roovers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-12  3:05 [gentoo-commits] repo/gentoo:master commit in: app-arch/snappy/ Ionen Wolkens
2023-03-20  7:26 Sam James
2023-03-19  3:22 Sam James
2023-02-22 16:16 Sam James
2022-10-19 10:07 WANG Xuerui
2022-03-06 23:49 Sam James
2022-03-06  7:55 Sam James
2022-02-28 10:08 Jakov Smolić
2022-02-28 10:08 Jakov Smolić
2022-02-27 22:42 Sam James
2022-02-27 22:42 Sam James
2021-10-18 23:49 Sam James
2021-10-17  0:13 Sam James
2021-10-16 22:05 Sam James
2021-10-16 14:02 Agostino Sarubbo
2021-10-16  7:10 Agostino Sarubbo
2021-08-23 17:01 Marek Szuba
2021-07-11 22:02 Marek Szuba
2021-06-03  9:12 Joonas Niilola
2021-05-05  9:56 Michał Górny
2021-03-13 11:29 Fabian Groffen
2020-06-08  8:56 Michał Górny
2020-05-04  9:37 Michał Górny
2020-04-04 14:12 Mart Raudsepp
2020-02-24 11:31 Agostino Sarubbo
2020-02-22 14:19 Sergei Trofimovich
2020-02-17 12:17 Agostino Sarubbo
2020-02-17 12:13 Agostino Sarubbo
2020-02-17 12:09 Agostino Sarubbo
2020-02-17 11:53 Agostino Sarubbo
2020-02-17 11:45 Agostino Sarubbo
2020-02-16 21:14 Thomas Deutschmann
2019-11-03 14:01 Michał Górny
2019-05-15  4:48 Aaron Bauman
2018-07-28  1:11 Mikle Kolyada
2018-06-13  7:21 Michał Górny
2018-05-27 12:34 Michał Górny
2018-05-27  8:41 Michał Górny
2018-03-28 19:35 Matt Turner
2018-03-03 13:12 Tobias Klausmann
2018-01-08  0:52 Mikle Kolyada
2018-01-02  8:14 Sergei Trofimovich
2017-11-19 20:44 Sergei Trofimovich
2017-10-28 22:08 Sergei Trofimovich
2017-07-31 18:57 Michał Górny
2016-10-05 19:02 Markus Meier
2016-09-26 15:22 Tobias Klausmann
2016-09-26  7:34 Jeroen Roovers
2016-09-25  9:23 Agostino Sarubbo
2016-09-25  9:22 Agostino Sarubbo
2016-05-31 12:22 Michał Górny
2016-05-31  6:45 Michał Górny
2016-05-31  6:45 Michał Górny
2016-04-06  4:39 Ian Delaney
2016-03-16 14:09 Agostino Sarubbo
2016-01-30 17:43 Tobias Klausmann
2016-01-27 15:06 Jeroen Roovers
2015-10-13  3:14 Ian Delaney
2015-10-13  1:25 Ian Delaney
2015-10-06 22:04 Chí-Thanh Christopher Nguyễn
2015-09-29 14:01 Tobias Klausmann
2015-09-21  4:58 Jeroen Roovers
2015-09-15  0:41 Tim Harder
2015-09-14  3:18 Jeroen Roovers
2015-09-01 18:37 Tobias Klausmann
2015-08-27  3:53 Tim Harder
2015-08-27  3:53 Tim Harder

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=1521286431.df1ed35261f25548fcc9bfe2f09eef43846175ec.jer@gentoo \
    --to=jer@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