public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-p2p/bitcoind/
Date: Wed,  4 Jan 2023 14:28:24 +0000 (UTC)	[thread overview]
Message-ID: <1672842485.37fabedb390902466744c36c4d9c43635c01abd9.arthurzam@gentoo> (raw)

commit:     37fabedb390902466744c36c4d9c43635c01abd9
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Wed Jan  4 14:28:05 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Wed Jan  4 14:28:05 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=37fabedb

net-p2p/bitcoind: Stabilize 22.0 x86, #889692

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 net-p2p/bitcoind/bitcoind-22.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-p2p/bitcoind/bitcoind-22.0.ebuild b/net-p2p/bitcoind/bitcoind-22.0.ebuild
index 77a077ac6a30..9cfae4858081 100644
--- a/net-p2p/bitcoind/bitcoind-22.0.ebuild
+++ b/net-p2p/bitcoind/bitcoind-22.0.ebuild
@@ -19,7 +19,7 @@ SRC_URI="
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~mips ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~arm ~arm64 ~mips ~ppc ~ppc64 x86 ~amd64-linux ~x86-linux"
 IUSE="+asm +berkdb examples +external-signer knots nat-pmp sqlite systemtap test upnp +wallet zeromq"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2023-01-04 14:28 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 14:28 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-31  2:23 [gentoo-commits] repo/gentoo:master commit in: net-p2p/bitcoind/ Sam James
2023-10-24  9:14 Joonas Niilola
2023-10-24  9:14 Joonas Niilola
2023-10-19 17:49 Florian Schmaus
2023-03-19  4:21 Sam James
2023-01-05  5:05 Sam James
2023-01-04 14:28 Arthur Zamarin
2023-01-04  9:42 Sam James
2022-09-30 23:24 Sam James
2022-09-04 13:03 David Seifert
2022-08-26 10:46 Sam James
2022-01-15  8:30 Joonas Niilola
2021-12-17  8:13 Florian Schmaus
2021-11-18  6:55 Joonas Niilola
2021-07-11 14:42 Craig Andrews
2021-07-10  2:21 Georgy Yakovlev
2021-07-10  1:19 Craig Andrews
2021-05-28  3:17 Sam James
2021-05-28  2:27 Sam James
2021-02-07  9:03 Joonas Niilola
2021-01-21 23:23 Sam James
2020-08-30 17:14 Thomas Deutschmann
2020-08-29 13:23 Sam James
2020-08-19  0:54 Craig Andrews
2020-06-17  1:52 Craig Andrews
2020-03-07 21:15 Craig Andrews
2020-03-07 21:15 Craig Andrews
2020-03-07 21:15 Craig Andrews
2020-02-08 16:25 David Seifert
2019-01-15 14:48 Craig Andrews
2019-01-11 21:38 Craig Andrews
2018-09-30 19:05 Virgil Dupras
2018-09-25 11:17 Agostino Sarubbo
2018-09-21 12:40 Virgil Dupras
2018-03-31 23:09 Michał Górny
2018-03-28 19:09 Matt Turner
2018-03-18 13:57 Mikle Kolyada
2018-02-22  9:05 Agostino Sarubbo
2018-01-28 23:19 Andreas Sturmlechner
2018-01-26 23:24 Thomas Deutschmann
2018-01-19 18:40 Andreas Sturmlechner
2017-12-31 16:20 Mike Gilbert
2017-03-11 18:33 Anthony G. Basile
2016-12-20  9:08 Agostino Sarubbo
2016-12-19 19:56 Tobias Klausmann
2016-07-01 23:28 Anthony G. Basile
2016-03-24 19:30 Anthony G. Basile
2015-11-27 20:01 Anthony G. Basile

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=1672842485.37fabedb390902466744c36c4d9c43635c01abd9.arthurzam@gentoo \
    --to=arthurzam@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