From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ml/dose3/
Date: Wed, 10 Feb 2021 15:10:04 +0000 (UTC) [thread overview]
Message-ID: <1612969800.aa5984801dc0db2dc5ff832dff15a91b6d9fce4a.sam@gentoo> (raw)
commit: aa5984801dc0db2dc5ff832dff15a91b6d9fce4a
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Feb 10 15:10:00 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Feb 10 15:10:00 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aa598480
dev-ml/dose3: add upper bound on OCaml for 5.0.1-r1
Safe string issues.
Package-Manager: Portage-3.0.14, Repoman-3.0.2
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-ml/dose3/{dose3-5.0.1-r1.ebuild => dose3-5.0.1-r2.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ml/dose3/dose3-5.0.1-r1.ebuild b/dev-ml/dose3/dose3-5.0.1-r2.ebuild
similarity index 97%
rename from dev-ml/dose3/dose3-5.0.1-r1.ebuild
rename to dev-ml/dose3/dose3-5.0.1-r2.ebuild
index 76e47f4749f..a90a3f4b1e8 100644
--- a/dev-ml/dose3/dose3-5.0.1-r1.ebuild
+++ b/dev-ml/dose3/dose3-5.0.1-r2.ebuild
@@ -14,7 +14,7 @@ KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64 ~x86"
IUSE="+ocamlopt parmap zip bzip2 xml curl rpm4 test"
RDEPEND="
- >=dev-lang/ocaml-3.12:=[ocamlopt?]
+ <dev-lang/ocaml-4.09.0:=[ocamlopt=]
dev-ml/cudf:=
>=dev-ml/extlib-1.7.0:=
dev-ml/re:=
next reply other threads:[~2021-02-10 15:10 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 15:10 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-06 17:46 [gentoo-commits] repo/gentoo:master commit in: dev-ml/dose3/ Alfredo Tupone
2025-04-28 0:17 Sam James
2025-03-13 20:02 Alfredo Tupone
2024-10-15 15:25 Arthur Zamarin
2024-07-15 13:57 Alfredo Tupone
2023-04-06 6:35 Alfredo Tupone
2023-03-30 17:57 Arthur Zamarin
2023-03-30 17:35 Arthur Zamarin
2023-03-17 14:46 Arthur Zamarin
2023-03-17 7:17 Arthur Zamarin
2023-03-17 2:29 Sam James
2022-12-05 17:56 Alfredo Tupone
2022-12-05 17:51 Alfredo Tupone
2022-12-04 21:18 Alfredo Tupone
2022-01-15 18:20 Alfredo Tupone
2021-11-05 21:50 Alfredo Tupone
2021-10-29 5:55 Agostino Sarubbo
2021-10-18 23:49 Sam James
2021-10-17 19:09 Sam James
2021-10-16 14:02 Agostino Sarubbo
2021-10-14 10:00 Michał Górny
2021-10-14 9:44 Sam James
2021-10-12 7:13 Agostino Sarubbo
2021-10-12 7:10 Agostino Sarubbo
2021-10-06 1:25 Sam James
2021-09-07 0:09 Sam James
2021-07-28 1:48 Sam James
2021-07-22 20:23 Alfredo Tupone
2021-06-09 22:17 Sam James
2021-06-08 4:12 Sam James
2021-06-06 23:55 Sam James
2021-03-14 0:48 Sam James
2021-02-19 21:24 Alfredo Tupone
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-10 1:55 Sam James
2021-02-09 22:57 Sam James
2021-01-27 6:34 Sam James
2021-01-26 17:34 Alfredo Tupone
2020-11-28 18:37 Aaron Bauman
2020-10-28 3:36 Sam James
2020-10-24 0:38 Sam James
2017-08-04 21:07 Amy Liffey
2017-08-02 11:23 Alexis Ballier
2017-04-05 17:50 Markus Meier
2017-04-05 9:51 Michael Weber
2016-08-13 14:23 Alexis Ballier
2016-05-03 9:14 Alexis Ballier
2016-04-22 13:01 Alexis Ballier
2016-03-01 18:47 Alexis Ballier
2016-01-22 10:47 Alexis Ballier
2016-01-19 11: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=1612969800.aa5984801dc0db2dc5ff832dff15a91b6d9fce4a.sam@gentoo \
--to=sam@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