From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ml/opam-installer/
Date: Fri, 17 Mar 2023 11:32:44 +0000 (UTC) [thread overview]
Message-ID: <1679052750.3db05342521969ad2917752033481e1a7db69483.arthurzam@gentoo> (raw)
commit: 3db05342521969ad2917752033481e1a7db69483
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 17 11:32:30 2023 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Fri Mar 17 11:32:30 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3db05342
dev-ml/opam-installer: Stabilize 2.1.2-r1 ppc64, #901649
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-ml/opam-installer/opam-installer-2.1.2-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ml/opam-installer/opam-installer-2.1.2-r1.ebuild b/dev-ml/opam-installer/opam-installer-2.1.2-r1.ebuild
index 49fe46cbc672..70653473715d 100644
--- a/dev-ml/opam-installer/opam-installer-2.1.2-r1.ebuild
+++ b/dev-ml/opam-installer/opam-installer-2.1.2-r1.ebuild
@@ -17,7 +17,7 @@ OPAM_INSTALLER="${S}/_build/install/default/bin/opam-installer"
LICENSE="LGPL-2.1"
SLOT="0/${PV}"
-KEYWORDS="amd64 arm arm64 ~ppc ~ppc64 ~riscv ~x86"
+KEYWORDS="amd64 arm arm64 ~ppc ppc64 ~riscv ~x86"
IUSE="+ocamlopt"
PATCHES=( "${WORKDIR}"/opam-2.1.0-dose3-6.patch )
next reply other threads:[~2023-03-17 11:32 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 11:32 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-23 12:41 [gentoo-commits] repo/gentoo:master commit in: dev-ml/opam-installer/ Alfredo Tupone
2024-10-14 19:57 Alfredo Tupone
2024-09-02 7:29 Arthur Zamarin
2024-08-23 13:00 Arthur Zamarin
2024-08-18 17:47 Sam James
2024-08-18 17:47 Sam James
2024-08-18 17:47 Sam James
2024-07-19 16:55 Alfredo Tupone
2024-07-18 6:07 Alfredo Tupone
2024-07-15 10:06 Alfredo Tupone
2024-01-19 23:08 Ionen Wolkens
2023-12-22 5:07 Sam James
2023-05-13 19:46 Alfredo Tupone
2023-03-17 11:47 Arthur Zamarin
2023-03-17 11:32 Arthur Zamarin
2023-03-17 11:32 Arthur Zamarin
2023-03-17 11:32 Arthur Zamarin
2023-03-03 21:16 Alfredo Tupone
2023-02-23 23:38 Sam James
2022-07-23 23:52 Sam James
2022-06-21 1:53 Sam James
2022-02-01 9:37 Alfredo Tupone
2022-01-18 12:24 Sam James
2022-01-13 20:25 Arthur Zamarin
2022-01-13 6:34 Sam James
2022-01-11 0:45 Sam James
2022-01-10 20:07 Arthur Zamarin
2022-01-10 19:56 Arthur Zamarin
2021-11-06 3:40 Sam James
2021-11-06 3:36 Sam James
2021-11-06 3:36 Sam James
2021-10-14 9:44 Sam James
2021-10-03 7:11 Sam James
2021-10-02 21:25 Sam James
2021-10-02 19:16 Sam James
2021-10-02 19:16 Sam James
2021-10-02 19:16 Sam James
2021-10-02 19:16 Sam James
2021-07-29 6:45 Agostino Sarubbo
2021-07-28 2:38 Sam James
2021-07-28 1:48 Sam James
2021-06-29 18:24 Alfredo Tupone
2021-05-10 15:20 Alfredo Tupone
2021-03-15 4:02 Sam James
2021-03-15 3:47 Sam James
2021-03-14 1:20 Sam James
2021-03-14 0:48 Sam James
2021-03-13 14:05 Sam James
2021-03-04 14:28 Agostino Sarubbo
2021-02-11 6:31 Sam James
2021-02-11 6:26 Sam James
2021-02-10 18:53 Sam James
2021-02-10 16:33 Sam James
2021-02-09 19:56 Sam James
2021-02-08 17:21 Sam James
2021-02-08 17:21 Sam James
2021-01-27 18:25 Alfredo Tupone
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=1679052750.3db05342521969ad2917752033481e1a7db69483.arthurzam@gentoo \
--to=arthurzam@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