public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-p2p/bitcoin-core/
Date: Wed, 12 Feb 2025 05:00:04 +0000 (UTC)	[thread overview]
Message-ID: <1739336388.c8f012ef169a1fd8a404e90733e09d57e6b7e76d.sam@gentoo> (raw)

commit:     c8f012ef169a1fd8a404e90733e09d57e6b7e76d
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Feb 12 04:59:48 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Feb 12 04:59:48 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c8f012ef

net-p2p/bitcoin-core: Stabilize 28.1 arm, #949631

Signed-off-by: Sam James <sam <AT> gentoo.org>

 net-p2p/bitcoin-core/bitcoin-core-28.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-p2p/bitcoin-core/bitcoin-core-28.1.ebuild b/net-p2p/bitcoin-core/bitcoin-core-28.1.ebuild
index 4eec8fc940d0..27c995938f74 100644
--- a/net-p2p/bitcoin-core/bitcoin-core-28.1.ebuild
+++ b/net-p2p/bitcoin-core/bitcoin-core-28.1.ebuild
@@ -17,7 +17,7 @@ S="${WORKDIR}/${PN/-core}-${PV/_rc/rc}"
 LICENSE="MIT"
 SLOT="0"
 if [[ "${PV}" != *_rc* ]] ; then
-	KEYWORDS="~amd64 ~arm arm64 ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux"
+	KEYWORDS="~amd64 arm arm64 ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux"
 fi
 IUSE="+asm +berkdb +cli +daemon dbus examples +external-signer gui kde +man nat-pmp +qrcode +sqlite +system-libsecp256k1 systemtap test test-full upnp zeromq"
 RESTRICT="!test? ( test )"


             reply	other threads:[~2025-02-12  5:00 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12  5:00 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-30 20:09 [gentoo-commits] repo/gentoo:master commit in: net-p2p/bitcoin-core/ Florian Schmaus
2025-10-30 20:09 Florian Schmaus
2025-10-30 20:09 Florian Schmaus
2025-09-19 14:11 Sam James
2025-05-21 10:56 Arthur Zamarin
2025-05-21 10:56 Arthur Zamarin
2025-05-20 21:27 Sam James
2025-05-20 21:27 Sam James
2025-04-20  8:18 Sam James
2025-04-20  8:18 Sam James
2025-04-20  8:18 Sam James
2025-04-20  8:18 Sam James
2025-03-31 15:33 Andreas Sturmlechner
2025-02-13  8:48 Joonas Niilola
2025-02-12  5:00 Sam James
2025-02-12  5:00 Sam James
2025-01-09  8:26 Florian Schmaus
2024-12-20  0:02 Sam James
2024-12-13  7:39 Joonas Niilola
2024-12-10 15:22 Sam James
2024-12-10 15:22 Sam James
2024-12-10 14:37 Arthur Zamarin
2024-11-09 10:08 Arthur Zamarin
2024-11-09  9:57 Arthur Zamarin
2024-11-07  9:16 Sam James
2024-11-06 10:02 Florian Schmaus
2024-10-08 19:33 Florian Schmaus
2024-09-22 11:27 Sam James
2024-08-31  2:23 Sam James
2024-07-29  7:33 Joonas Niilola
2024-06-26  9:27 Florian Schmaus
2024-06-20 11:28 Florian Schmaus
2024-06-20 11:27 Florian Schmaus
2024-06-20 11:27 Florian Schmaus
2024-06-13  7:47 Florian Schmaus
2024-04-17 10:10 Florian Schmaus
2024-04-03 17:38 Florian Schmaus
2024-03-07 15:19 Sam James
2024-03-07 15:19 Sam James
2024-03-07 15:19 Sam James
2023-12-13  7:47 Florian Schmaus
2023-10-25  8:37 Florian Schmaus
2023-10-25  8:37 Florian Schmaus
2023-10-25  8:37 Florian Schmaus
2023-10-24  9:14 Joonas Niilola
2023-10-24  9:14 Joonas Niilola
2023-10-09 13:14 Florian Schmaus

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=1739336388.c8f012ef169a1fd8a404e90733e09d57e6b7e76d.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