public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petr Vaněk" <arkamar@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/watchman/
Date: Mon, 18 Nov 2024 14:00:00 +0000 (UTC)	[thread overview]
Message-ID: <1731938346.00e63cc01ca3cd6f017e9a2f0c4870ec5b1796bb.arkamar@gentoo> (raw)

commit:     00e63cc01ca3cd6f017e9a2f0c4870ec5b1796bb
Author:     Petr Vaněk <arkamar <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 18 13:54:30 2024 +0000
Commit:     Petr Vaněk <arkamar <AT> gentoo <DOT> org>
CommitDate: Mon Nov 18 13:59:06 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=00e63cc0

dev-util/watchman: restrict <libfmt-10 in 2023.06.19.00

Watchman 2023.06.19 fails to compile with >=libfmt-10 [1]. The issue is
already addressed in more recent versions.

[1] https://github.com/facebook/watchman/issues/1140

Signed-off-by: Petr Vaněk <arkamar <AT> gentoo.org>

 ...atchman-2023.06.19.00-r1.ebuild => watchman-2023.06.19.00-r2.ebuild} | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/dev-util/watchman/watchman-2023.06.19.00-r1.ebuild b/dev-util/watchman/watchman-2023.06.19.00-r2.ebuild
similarity index 98%
rename from dev-util/watchman/watchman-2023.06.19.00-r1.ebuild
rename to dev-util/watchman/watchman-2023.06.19.00-r2.ebuild
index 18a9a02d8d3d..591c4924066c 100644
--- a/dev-util/watchman/watchman-2023.06.19.00-r1.ebuild
+++ b/dev-util/watchman/watchman-2023.06.19.00-r2.ebuild
@@ -148,6 +148,7 @@ IUSE="llvm-libunwind python"
 REQUIRED_USE="python? ( ${PYTHON_REQUIRED_USE} )"
 
 # See https://github.com/facebook/watchman/blob/main/CMakeLists.txt#L342 for libevent
+# <libfmt-10 https://github.com/facebook/watchman/issues/1140
 RDEPEND="
 	dev-libs/libevent:=
 	dev-libs/libpcre2
@@ -155,6 +156,7 @@ RDEPEND="
 	~dev-cpp/folly-${PV}:=
 	dev-cpp/glog:=
 	>=dev-libs/libfmt-8.1.1-r1:=
+	<dev-libs/libfmt-10
 	dev-libs/openssl:=
 	llvm-libunwind? ( sys-libs/llvm-libunwind:= )
 	!llvm-libunwind? ( sys-libs/libunwind:= )


             reply	other threads:[~2024-11-18 14:00 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18 14:00 Petr Vaněk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-05 10:06 [gentoo-commits] repo/gentoo:master commit in: dev-util/watchman/ Arthur Zamarin
2024-11-23 20:16 Sam James
2024-11-11 22:25 Sam James
2024-05-28 19:01 Michał Górny
2023-11-25  6:21 Sam James
2023-11-25  6:21 Sam James
2023-06-24  8:29 Arthur Zamarin
2023-06-02 12:45 Sam James
2023-06-02 12:40 Sam James
2023-05-04  9:03 Sam James
2023-05-01  1:43 Sam James
2023-04-14  3:39 Sam James
2023-02-16  3:29 Sam James
2023-02-16  3:29 Sam James
2023-02-06 21:25 Sam James
2022-12-16 20:48 Arthur Zamarin
2022-09-18  0:35 Sam James
2022-09-18  0:35 Sam James
2022-09-06  4:18 Sam James
2022-08-29 20:13 Sam James
2022-08-23  3:30 Sam James
2022-08-15 17:08 Sam James
2022-08-13 15:09 Sam James
2022-07-09  4:47 Sam James
2022-05-16 12:51 Agostino Sarubbo
2022-04-17 16:44 Sam James
2022-04-16  3:07 Sam James
2022-04-05  3:08 Sam James
2022-04-05  3:08 Sam James
2022-04-01  3:53 Sam James
2022-04-01  3:53 Sam James
2022-03-22  1:48 Sam James
2022-03-21 16:37 Patrice Clement
2022-03-18  6:16 Sam James
2022-03-09 15:34 Sam James
2022-03-02  3:20 Sam James
2021-06-12  9:47 Patrice Clement
2020-11-13  8:13 Patrice Clement

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=1731938346.00e63cc01ca3cd6f017e9a2f0c4870ec5b1796bb.arkamar@gentoo \
    --to=arkamar@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