public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Simone Caronni <negativo17@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/bitcoin-core] f43: Add comment
Date: Mon, 20 Jul 2026 13:41:37 GMT [thread overview]
Message-ID: <178455489791.1.9808215362513017214.rpms-bitcoin-core-1858e5269c98@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/bitcoin-core
Branch : f43
Commit : 1858e5269c985a37fe919ba4a44825d9af45dd1c
Author : Simone Caronni <negativo17@gmail.com>
Date : 2026-07-20T15:41:27+02:00
Stats : +1/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/bitcoin-core/c/1858e5269c985a37fe919ba4a44825d9af45dd1c?branch=f43
Log:
Add comment
---
diff --git a/bitcoin-core.spec b/bitcoin-core.spec
index bf51126..462a573 100644
--- a/bitcoin-core.spec
+++ b/bitcoin-core.spec
@@ -162,7 +162,7 @@ grep -q $(sha256sum %{SOURCE0}) %{SOURCE2}
cp -p %{SOURCE12} %{SOURCE13} %{SOURCE14} %{SOURCE15} .
%build
-# Segfaults on GCC 16.1 (fixed in 16.2)
+# Segfaults on GCC 16.1 (fixed in 16.2): https://github.com/bitcoin/bitcoin/issues/35282
sed -i -e '/cluster_linearize_tests.cpp/d' src/test/CMakeLists.txt
# Bitcoin kernel library used only as part of the testing for now:
reply other threads:[~2026-07-20 13:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178455489791.1.9808215362513017214.rpms-bitcoin-core-1858e5269c98@fedoraproject.org \
--to=negativo17@gmail.com \
--cc=git-commits@fedoraproject.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