From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ml/alcotest/
Date: Thu, 6 May 2021 07:22:24 +0000 (UTC) [thread overview]
Message-ID: <1620285732.fbf2c9274aa6eeef2e7bd58bb0f9fe535cdc60e1.slyfox@gentoo> (raw)
commit: fbf2c9274aa6eeef2e7bd58bb0f9fe535cdc60e1
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Thu May 6 07:09:51 2021 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Thu May 6 07:22:12 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fbf2c927
dev-ml/alcotest: stable 1.2.3-r3 for ppc64
stable wrt bug #783582
Package-Manager: Portage-3.0.18, Repoman-3.0.3
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-ml/alcotest/alcotest-1.2.3-r3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ml/alcotest/alcotest-1.2.3-r3.ebuild b/dev-ml/alcotest/alcotest-1.2.3-r3.ebuild
index 0ca71621477..cf09b59a6db 100644
--- a/dev-ml/alcotest/alcotest-1.2.3-r3.ebuild
+++ b/dev-ml/alcotest/alcotest-1.2.3-r3.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/mirage/alcotest/archive/${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="ISC"
SLOT="0/${PV}"
-KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64 ~x86"
+KEYWORDS="~amd64 ~arm ~arm64 ~ppc ppc64 ~x86"
IUSE="+ocamlopt"
RDEPEND="
next reply other threads:[~2021-05-06 7:22 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 7:22 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-21 18:41 [gentoo-commits] repo/gentoo:master commit in: dev-ml/alcotest/ Arthur Zamarin
2024-10-21 18:41 Arthur Zamarin
2024-10-20 4:46 Sam James
2024-10-20 4:46 Sam James
2024-07-28 16:56 Alfredo Tupone
2024-07-14 19:06 Alfredo Tupone
2024-07-02 14:50 Maciej Barć
2024-07-02 14:50 Maciej Barć
2024-01-24 18:30 Alfredo Tupone
2023-07-29 6:24 Alfredo Tupone
2023-07-08 16:43 Alfredo Tupone
2023-06-15 18:20 Arthur Zamarin
2023-06-15 18:20 Arthur Zamarin
2023-06-09 18:02 Arthur Zamarin
2023-06-09 16:52 Arthur Zamarin
2023-06-09 15:27 Arthur Zamarin
2023-06-09 15:27 Arthur Zamarin
2023-04-24 13:51 Alfredo Tupone
2023-04-17 8:59 Alfredo Tupone
2023-02-24 22:20 Sam James
2023-02-24 16:56 Sam James
2023-02-20 20:27 Arthur Zamarin
2023-01-27 0:30 Sam James
2022-12-24 15:54 Alfredo Tupone
2022-10-30 9:13 Alfredo Tupone
2022-10-13 13:05 Alfredo Tupone
2022-06-21 1:53 Sam James
2022-04-18 21:07 Jakov Smolić
2021-11-03 21:16 Alfredo Tupone
2021-10-13 20:37 Sam James
2021-10-13 20:35 Sam James
2021-10-12 7:14 Agostino Sarubbo
2021-10-11 12:17 Agostino Sarubbo
2021-10-11 5:45 Sam James
2021-10-11 5:16 Sam James
2021-07-27 18:57 Alfredo Tupone
2021-06-03 0:45 Sam James
2021-05-16 19:02 Sam James
2021-05-16 0:07 Sam James
2021-05-15 19:17 Sam James
2021-05-15 2:01 Sam James
2021-03-07 18:00 Alfredo Tupone
2021-02-21 9:44 Sam James
2021-02-21 8:11 Sam James
2021-02-21 7:28 Sam James
2021-02-10 16:38 Sam James
2021-02-10 16:30 Sam James
2021-02-10 15:31 Sam James
2021-02-09 23:09 Sam James
2021-02-09 22:48 Sam James
2021-02-09 22:47 Sam James
2021-02-08 17:21 Sam James
2020-09-24 19:53 Aaron Bauman
2017-08-26 12:03 Alexis Ballier
2017-08-06 7:40 Alexis Ballier
2017-08-06 7:40 Alexis Ballier
2017-06-28 9:35 Alexis Ballier
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=1620285732.fbf2c9274aa6eeef2e7bd58bb0f9fe535cdc60e1.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