From: "Alfredo Tupone" <tupone@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ml/opam/
Date: Wed, 20 Jul 2022 11:53:39 +0000 (UTC) [thread overview]
Message-ID: <1658317997.a08fcfc37414028a3600023457fc7957c5add4a8.tupone@gentoo> (raw)
commit: a08fcfc37414028a3600023457fc7957c5add4a8
Author: Alfredo Tupone <tupone <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 20 11:52:44 2022 +0000
Commit: Alfredo Tupone <tupone <AT> gentoo <DOT> org>
CommitDate: Wed Jul 20 11:53:17 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a08fcfc3
dev-ml/opam: RESTRICT test
Closes: https://bugs.gentoo.org/838658
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Alfredo Tupone <tupone <AT> gentoo.org>
dev-ml/opam/opam-2.1.2.ebuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-ml/opam/opam-2.1.2.ebuild b/dev-ml/opam/opam-2.1.2.ebuild
index 566843487a72..360e33347b42 100644
--- a/dev-ml/opam/opam-2.1.2.ebuild
+++ b/dev-ml/opam/opam-2.1.2.ebuild
@@ -15,6 +15,7 @@ LICENSE="LGPL-2.1-with-linking-exception"
SLOT="0/${PV}"
KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64 ~riscv ~x86"
IUSE="+ocamlopt"
+RESTRICT="test" #see bugs 838658
RDEPEND="
dev-ml/cmdliner:=
next reply other threads:[~2022-07-20 11:53 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 11:53 Alfredo Tupone [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-13 19:38 [gentoo-commits] repo/gentoo:master commit in: dev-ml/opam/ 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:58 Alfredo Tupone
2024-07-18 6:07 Alfredo Tupone
2024-07-15 10:38 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-03 21:16 Alfredo Tupone
2023-02-23 23:38 Sam James
2022-11-19 10:34 Arthur Zamarin
2022-11-19 10:34 Arthur Zamarin
2022-11-19 10:34 Arthur Zamarin
2022-09-18 0:37 Sam James
2022-09-18 0:37 Sam James
2022-09-09 17:19 Alfredo Tupone
2022-07-23 23:52 Sam James
2022-04-18 21:07 Jakov Smolić
2022-01-31 21:09 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-12-19 11:02 Sam James
2021-11-06 3:40 Sam James
2021-11-06 3:36 Sam James
2021-11-06 3:36 Sam James
2021-10-14 7:38 Sam James
2021-10-11 5:02 Sam James
2021-10-03 9:58 Alfredo Tupone
2021-10-02 21:10 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-10-01 19:09 Alfredo Tupone
2021-07-28 1:48 Sam James
2021-06-08 4:12 Sam James
2021-03-15 4:02 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-25 17:54 Sam James
2021-02-25 13:09 Sam James
2021-02-17 21:17 Alfredo Tupone
2021-02-08 17:21 Sam James
2021-02-08 15:38 Sam James
2021-02-08 15:38 Sam James
2020-10-17 2:31 Sam James
2017-08-02 11:23 Alexis Ballier
2017-07-07 17:48 Alexis Ballier
2017-04-12 19:20 Alexis Ballier
2017-04-05 17:50 Markus Meier
2017-04-05 9:51 Michael Weber
2017-03-11 9:14 Alexis Ballier
2016-12-27 12:40 Alexis Ballier
2016-02-06 16:25 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=1658317997.a08fcfc37414028a3600023457fc7957c5add4a8.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