public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Wright" <gienah@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ml/ppx_sexp_conv/
Date: Fri, 16 Oct 2020 15:17:15 +0000 (UTC)	[thread overview]
Message-ID: <1602861410.a8a4852a1031142db8cbc75e4aaa711b2ce00ce2.gienah@gentoo> (raw)

commit:     a8a4852a1031142db8cbc75e4aaa711b2ce00ce2
Author:     Mark Wright <gienah <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 16 15:15:31 2020 +0000
Commit:     Mark Wright <gienah <AT> gentoo <DOT> org>
CommitDate: Fri Oct 16 15:16:50 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a8a4852a

dev-ml/ppx_sexp_conv: Fix deps and compile fail

Thanks to Agostino Sarubbo for reporting.

Closes: https://bugs.gentoo.org/748714
Package-Manager: Portage-3.0.8, Repoman-3.0.1
Signed-off-by: Mark Wright <gienah <AT> gentoo.org>

 dev-ml/ppx_sexp_conv/ppx_sexp_conv-0.14.1.ebuild | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/dev-ml/ppx_sexp_conv/ppx_sexp_conv-0.14.1.ebuild b/dev-ml/ppx_sexp_conv/ppx_sexp_conv-0.14.1.ebuild
index a8e0f48c7c3..4f793b5ea46 100644
--- a/dev-ml/ppx_sexp_conv/ppx_sexp_conv-0.14.1.ebuild
+++ b/dev-ml/ppx_sexp_conv/ppx_sexp_conv-0.14.1.ebuild
@@ -15,11 +15,13 @@ KEYWORDS="~amd64 ~arm ~arm64"
 IUSE="+ocamlopt"
 
 DEPEND="
-	dev-ml/base:=
-	dev-ml/ocaml-migrate-parsetree:=
-		dev-ml/result:=
+	>=dev-ml/base-0.14.0:=
+	dev-ml/findlib:=
 	>=dev-ml/ppxlib-0.18.0:=
-		dev-ml/ocaml-compiler-libs:=
+		>=dev-ml/ocaml-compiler-libs-0.11.0:=
+		>=dev-ml/ocaml-migrate-parsetree-2.0.0:=
+			dev-ml/cinaps:=
+	dev-ml/sexplib0:=
 "
 RDEPEND="${DEPEND}"
 


             reply	other threads:[~2020-10-16 15:17 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 15:17 Mark Wright [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-29 22:29 [gentoo-commits] repo/gentoo:master commit in: dev-ml/ppx_sexp_conv/ Alfredo Tupone
2023-06-30 13:14 Alfredo Tupone
2023-03-25 13:07 Arthur Zamarin
2023-03-25  1:47 Sam James
2023-03-25  1:47 Sam James
2023-03-25  1:43 Sam James
2023-03-16 13:42 Alfredo Tupone
2023-03-09 21:18 Alfredo Tupone
2023-01-28 13:26 Alfredo Tupone
2022-04-24  8:57 Alfredo Tupone
2022-04-23 18:46 Alfredo Tupone
2022-04-22 18:03 Alfredo Tupone
2021-11-15 19:41 Agostino Sarubbo
2021-11-15 16:29 Agostino Sarubbo
2021-11-02 10:20 Sam James
2021-11-02 10:20 Sam James
2021-10-20  7:02 Agostino Sarubbo
2021-10-20  6:56 Agostino Sarubbo
2021-10-15  3:29 Sam James
2021-08-03 11:03 Sam James
2021-07-31 22:12 Sam James
2021-07-30 15:14 Agostino Sarubbo
2021-07-30  6:13 Sam James
2021-07-29  6:45 Agostino Sarubbo
2021-07-28  3:12 Sam James
2021-07-12 20:35 Alfredo Tupone
2021-07-12 19:57 Alfredo Tupone
2021-03-07 20:12 Alfredo Tupone
2021-02-09 18:31 Sam James
2021-01-24 20:43 Sam James
2018-02-14 14:30 Thomas Deutschmann
2017-09-10 14:45 Sergei Trofimovich
2017-08-15  7:26 Alexis Ballier
2017-06-25 14:42 Alexis Ballier
2017-04-17  8:35 Alexis Ballier
2017-04-17  8:35 Alexis Ballier
2017-04-15 10:27 Alexis Ballier
2017-01-24 11:40 Alexis Ballier
2016-03-22  9:20 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=1602861410.a8a4852a1031142db8cbc75e4aaa711b2ce00ce2.gienah@gentoo \
    --to=gienah@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