public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergey Alirzaev" <zl29ah@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: net-p2p/monero/
Date: Sat, 14 Dec 2024 16:44:23 +0000 (UTC)	[thread overview]
Message-ID: <1734194644.6b08df89271278304b3a498498fd7aa0101aafe3.zl29ah@gentoo> (raw)

commit:     6b08df89271278304b3a498498fd7aa0101aafe3
Author:     Sergey Alirzaev <l29ah <AT> riseup <DOT> net>
AuthorDate: Sat Dec 14 16:44:04 2024 +0000
Commit:     Sergey Alirzaev <zl29ah <AT> gmail <DOT> com>
CommitDate: Sat Dec 14 16:44:04 2024 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=6b08df89

net-p2p/monero: limit boost dep version

https://github.com/monero-project/monero/issues/9596

Signed-off-by: Sergey Alirzaev <l29ah <AT> riseup.net>

 net-p2p/monero/monero-0.18.3.4-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-p2p/monero/monero-0.18.3.4-r1.ebuild b/net-p2p/monero/monero-0.18.3.4-r1.ebuild
index 70cbb2770..239eec451 100644
--- a/net-p2p/monero/monero-0.18.3.4-r1.ebuild
+++ b/net-p2p/monero/monero-0.18.3.4-r1.ebuild
@@ -26,7 +26,7 @@ RESTRICT="test"
 DEPEND="
 	acct-group/monero
 	acct-user/monero
-	dev-libs/boost:=[nls]
+	<dev-libs/boost-1.87:=[nls]
 	dev-libs/libsodium:=
 	dev-libs/openssl:=
 	dev-libs/randomx


             reply	other threads:[~2024-12-14 16:44 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-14 16:44 Sergey Alirzaev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-22 15:48 [gentoo-commits] repo/proj/guru:dev commit in: net-p2p/monero/ Filip Kobierski
2025-06-22 15:48 Filip Kobierski
2025-06-22 15:48 Filip Kobierski
2025-06-16 13:36 Filip Kobierski
2025-06-16 13:36 Filip Kobierski
2025-06-08  0:40 Filip Kobierski
2025-06-07 12:33 Sergey Alirzaev
2025-06-02 14:47 Filip Kobierski
2025-05-06 17:58 Filip Kobierski
2025-03-31 11:30 Sergey Alirzaev
2024-12-18  0:27 Julien Roy
2024-09-25 14:46 Filip Kobierski
2024-09-25 14:46 Filip Kobierski
2024-09-25 14:46 Filip Kobierski
2024-09-17  9:20 Filip Kobierski
2024-08-15  0:35 Sergey Alirzaev
2024-07-26 14:07 Filip Kobierski
2024-06-29  9:42 Sergey Alirzaev
2024-05-29 10:26 Sergey Alirzaev
2024-03-16 13:19 Sergey Alirzaev
2024-03-09 20:07 Sergey Alirzaev
2024-01-07  7:24 Takuya Wakazono
2023-11-23 17:46 Alfred Persson Forsberg
2023-10-03  0:01 Sergey Alirzaev
2023-10-02  0:01 Sergey Alirzaev
2023-06-07  1:42 YiFei Zhu
2023-04-04 13:42 Sergey Alirzaev
2023-02-26  1:02 Sergey Alirzaev
2023-01-02 12:17 Sergey Alirzaev
2023-01-01 17:10 Sergey Alirzaev
2022-09-25  0:17 Sergey Alirzaev
2022-09-17 20:23 Sergey Alirzaev
2022-07-01 16:57 Alfred Persson Forsberg
2022-04-30  6:09 Dex Conner
2022-04-16 10:12 Dex Conner
2021-09-09 23:28 Sergey Alirzaev
2021-05-07 13:25 Sergey Alirzaev
2021-04-28  2:16 Theo Anderson
2021-04-28  2:16 Theo Anderson
2021-04-27 23:24 [gentoo-commits] repo/proj/guru:master " Theo Anderson
2021-04-27 23:23 ` [gentoo-commits] repo/proj/guru:dev " Theo Anderson
2021-01-08 21:18 Theo Anderson
2021-01-08 21:18 Theo Anderson
2021-01-04 21:41 Theo Anderson
2020-12-31  8:08 Theo Anderson
2020-12-29 10:41 Theo Anderson
2020-12-29 10:41 Theo Anderson
2020-12-29 10:41 Theo Anderson

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=1734194644.6b08df89271278304b3a498498fd7aa0101aafe3.zl29ah@gentoo \
    --to=zl29ah@gmail.com \
    --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