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-cpp/nlohmann_json/
Date: Fri, 11 Dec 2020 23:07:23 +0000 (UTC)	[thread overview]
Message-ID: <1607727976.96df68e98da7179d2503307dc84a7f0846422619.slyfox@gentoo> (raw)

commit:     96df68e98da7179d2503307dc84a7f0846422619
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 11 23:06:16 2020 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Dec 11 23:06:16 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=96df68e9

dev-cpp/nlohmann_json: stable 3.9.1 for ppc

stable wrt bug #758836

Package-Manager: Portage-3.0.12, Repoman-3.0.2
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>

 dev-cpp/nlohmann_json/nlohmann_json-3.9.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-cpp/nlohmann_json/nlohmann_json-3.9.1.ebuild b/dev-cpp/nlohmann_json/nlohmann_json-3.9.1.ebuild
index cbfe14e3ebf..80a5933f0f9 100644
--- a/dev-cpp/nlohmann_json/nlohmann_json-3.9.1.ebuild
+++ b/dev-cpp/nlohmann_json/nlohmann_json-3.9.1.ebuild
@@ -13,7 +13,7 @@ S="${WORKDIR}/json-${PV}"
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~ppc ~ppc64 x86"
+KEYWORDS="~amd64 ~arm64 ppc ~ppc64 x86"
 IUSE="doc test"
 #RESTRICT="!test? ( test )"
 # Need to report failing tests upstream


             reply	other threads:[~2020-12-11 23:07 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 23:07 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-30  3:07 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/nlohmann_json/ Sam James
2023-10-18 14:09 Sam James
2023-08-30  5:16 Sam James
2023-03-24 14:07 Arthur Zamarin
2023-03-22  5:44 Sam James
2023-02-16  5:52 WANG Xuerui
2022-12-18 12:16 Sam James
2022-08-13 17:43 Sam James
2022-08-13 13:32 Sam James
2022-08-12 21:02 Sam James
2022-06-07  8:24 Jakov Smolić
2022-04-17 19:24 Sam James
2022-02-19 15:22 Arthur Zamarin
2022-02-19 13:22 Jakov Smolić
2022-02-19 13:15 Jakov Smolić
2022-02-19  9:05 Arthur Zamarin
2022-01-11  4:33 Sam James
2022-01-09  9:17 Sam James
2021-10-17  0:03 Georgy Yakovlev
2021-10-09  4:21 Sam James
2021-09-25 18:11 Sam James
2021-09-02 13:27 Marek Szuba
2021-08-18  3:45 Sam James
2021-08-18  3:45 Sam James
2021-03-15  6:38 Sam James
2021-01-02 21:31 David Seifert
2021-01-02 21:08 Sam James
2020-12-16 21:34 Sam James
2020-12-11 23:10 Sergei Trofimovich
2020-12-10 21:41 Thomas Deutschmann
2020-10-11 20:31 Sam James
2020-10-10  6:31 Sam James
2020-10-07  7:09 Agostino Sarubbo
2020-10-07  6:53 Agostino Sarubbo
2020-10-07  6:50 Agostino Sarubbo
2020-10-07  6:42 Agostino Sarubbo
2020-10-04  0:26 Sam James
2020-01-16 15:45 Tim Harder
2019-09-27  5:49 Tim Harder
2019-09-27  5:49 Tim Harder
2019-09-26  6:52 Sergei Trofimovich
2019-07-23  8:23 Agostino Sarubbo
2019-07-21  8:25 Sergei Trofimovich
2019-07-18 14:32 Thomas Deutschmann
2019-06-28 23:26 Tim Harder
2019-04-11  5:37 Tim Harder
2019-02-17 17:40 Sergei Trofimovich
2018-12-29 21:04 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=1607727976.96df68e98da7179d2503307dc84a7f0846422619.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