From: "Alfredo Tupone" <tupone@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ml/ocaml-migrate-parsetree/
Date: Mon, 13 Feb 2023 21:13:51 +0000 (UTC) [thread overview]
Message-ID: <1676322808.e846d1fc9864ac594527ad287235392d9571af7b.tupone@gentoo> (raw)
commit: e846d1fc9864ac594527ad287235392d9571af7b
Author: Alfredo Tupone <tupone <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 13 21:12:43 2023 +0000
Commit: Alfredo Tupone <tupone <AT> gentoo <DOT> org>
CommitDate: Mon Feb 13 21:13:28 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e846d1fc
dev-ml/ocaml-migrate-parsetree: fix dep on ocaml
Closes: https://bugs.gentoo.org/894228
Signed-off-by: Alfredo Tupone <tupone <AT> gentoo.org>
...setree-1.8.0.ebuild => ocaml-migrate-parsetree-1.8.0-r1.ebuild} | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/dev-ml/ocaml-migrate-parsetree/ocaml-migrate-parsetree-1.8.0.ebuild b/dev-ml/ocaml-migrate-parsetree/ocaml-migrate-parsetree-1.8.0-r1.ebuild
similarity index 84%
rename from dev-ml/ocaml-migrate-parsetree/ocaml-migrate-parsetree-1.8.0.ebuild
rename to dev-ml/ocaml-migrate-parsetree/ocaml-migrate-parsetree-1.8.0-r1.ebuild
index 3516d59f1555..9bad2ee3e9f3 100644
--- a/dev-ml/ocaml-migrate-parsetree/ocaml-migrate-parsetree-1.8.0.ebuild
+++ b/dev-ml/ocaml-migrate-parsetree/ocaml-migrate-parsetree-1.8.0-r1.ebuild
@@ -1,7 +1,7 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2023 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
-EAPI=7
+EAPI=8
inherit dune
@@ -16,5 +16,6 @@ IUSE="+ocamlopt test"
RESTRICT="!test? ( test )"
DEPEND="dev-ml/cinaps:=
- dev-ml/ppx_derivers:="
+ dev-ml/ppx_derivers:=
+ <dev-lang/ocaml-4.13"
RDEPEND="${DEPEND}"
next reply other threads:[~2023-02-13 21:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 21:13 Alfredo Tupone [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-18 17:48 [gentoo-commits] repo/gentoo:master commit in: dev-ml/ocaml-migrate-parsetree/ Alfredo Tupone
2023-03-17 10:17 Arthur Zamarin
2023-03-17 2:43 Sam James
2022-12-16 11:06 Maciej Barć
2022-01-31 18:24 Alfredo Tupone
2021-10-29 5:55 Agostino Sarubbo
2021-10-29 5:54 Agostino Sarubbo
2021-10-18 23:49 Sam James
2021-10-17 0:13 Sam James
2021-10-16 14:02 Agostino Sarubbo
2021-10-16 7:10 Agostino Sarubbo
2021-10-15 3:25 Sam James
2021-10-15 3:23 Sam James
2021-07-08 18:14 Alfredo Tupone
2021-03-15 4:02 Sam James
2021-03-07 18:23 Alfredo Tupone
2021-01-16 17:39 Alfredo Tupone
2021-01-16 12:45 Alfredo Tupone
2021-01-15 21:54 Alfredo Tupone
2021-01-09 22:41 Alfredo Tupone
2020-10-16 9:06 Mark Wright
2020-10-15 12:20 Mark Wright
2020-10-13 12:54 Mark Wright
2017-11-04 11:06 Alexis Ballier
2017-10-14 11:13 Alexis Ballier
2017-10-14 11:13 Alexis Ballier
2017-10-04 8:02 Alexis Ballier
2017-08-24 8:55 Alexis Ballier
2017-08-15 5:41 Alexis Ballier
2017-08-15 5:41 Alexis Ballier
2017-08-15 5:41 Alexis Ballier
2017-08-02 11:23 Alexis Ballier
2017-07-30 15:39 Sergei Trofimovich
2017-07-29 12:34 Alexis Ballier
2017-07-24 5:56 Alexis Ballier
2017-07-24 5:56 Alexis Ballier
2017-04-18 20:10 Alexis Ballier
2017-04-01 12:24 Alexis Ballier
2017-04-01 12:24 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=1676322808.e846d1fc9864ac594527ad287235392d9571af7b.tupone@gentoo \
--to=tupone@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