From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ml/opam-format/
Date: Sat, 6 Nov 2021 03:40:16 +0000 (UTC) [thread overview]
Message-ID: <1636169949.b6c0dad4c5c045bb6012b4aed1db09fd333413ba.sam@gentoo> (raw)
commit: b6c0dad4c5c045bb6012b4aed1db09fd333413ba
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 6 03:39:09 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Nov 6 03:39:09 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b6c0dad4
dev-ml/opam-format: fix 2.0.10
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-ml/opam-format/opam-format-2.0.10.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-ml/opam-format/opam-format-2.0.10.ebuild b/dev-ml/opam-format/opam-format-2.0.10.ebuild
index 027845d265f..ace83b9a6ae 100644
--- a/dev-ml/opam-format/opam-format-2.0.10.ebuild
+++ b/dev-ml/opam-format/opam-format-2.0.10.ebuild
@@ -10,7 +10,6 @@ inherit dune
DESCRIPTION="Core libraries for opam"
HOMEPAGE="https://opam.ocaml.org/ https://github.com/ocaml/opam"
SRC_URI="https://github.com/ocaml/opam/archive/${PV/_/-}.tar.gz -> opam-${PV}.tar.gz"
-SRC_URI+=" https://dev.gentoo.org/~sam/distfiles/dev-ml/opam/opam-2.1.0-dose3-6.patch.xz"
S="${WORKDIR}/opam-${PV}"
OPAM_INSTALLER="${S}/opam-installer"
@@ -28,7 +27,8 @@ RDEPEND="
DEPEND="${RDEPEND}
dev-ml/cppo"
-PATCHES=( "${WORKDIR}"/opam-2.1.0-dose3-6.patch )
+# Cherry-picked from https://deb.debian.org/debian/pool/main/o/opam/opam_2.0.8-1.debian.tar.xz
+PATCHES=( "${FILESDIR}/debian-Port-to-Dose3-6.0.1.patch" )
src_prepare() {
default
next reply other threads:[~2021-11-06 3:40 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 3:40 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-19 17:25 [gentoo-commits] repo/gentoo:master commit in: dev-ml/opam-format/ Alfredo Tupone
2024-07-15 9:59 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-07-23 23:52 Sam James
2022-02-20 20:53 Alfredo Tupone
2022-01-31 20:45 Alfredo Tupone
2022-01-18 12:24 Sam James
2022-01-16 19:05 Alfredo Tupone
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:36 Sam James
2021-11-06 3:36 Sam James
2021-10-03 9:58 Alfredo Tupone
2021-10-02 19:16 Sam James
2021-10-02 19:16 Sam James
2021-10-02 19:16 Sam James
2021-10-01 18:08 Alfredo Tupone
2021-07-28 2:38 Sam James
2021-07-28 1:48 Sam James
2021-06-08 4:12 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-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 22:47 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 19:22 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=1636169949.b6c0dad4c5c045bb6012b4aed1db09fd333413ba.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