public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/bitcoin-tx/
Date: Sun, 18 Mar 2018 13:57:19 +0000 (UTC)	[thread overview]
Message-ID: <1521381436.741a0b23542934c0e7c28fedd45ae6686d4ac561.zlogene@gentoo> (raw)

commit:     741a0b23542934c0e7c28fedd45ae6686d4ac561
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 18 13:57:00 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Mar 18 13:57:16 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=741a0b23

dev-util/bitcoin-tx: arm stable wrt bug #644940

Package-Manager: Portage-2.3.24, Repoman-2.3.6

 dev-util/bitcoin-tx/bitcoin-tx-0.15.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-util/bitcoin-tx/bitcoin-tx-0.15.1.ebuild b/dev-util/bitcoin-tx/bitcoin-tx-0.15.1.ebuild
index 742aad14eb0..d4d855fafc4 100644
--- a/dev-util/bitcoin-tx/bitcoin-tx-0.15.1.ebuild
+++ b/dev-util/bitcoin-tx/bitcoin-tx-0.15.1.ebuild
@@ -18,7 +18,7 @@ DESCRIPTION="Command-line Bitcoin transaction tool"
 HOMEPAGE="https://bitcoincore.org/ https://bitcoinknots.org/"
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~mips ~ppc x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 arm ~arm64 ~mips ~ppc x86 ~amd64-linux ~x86-linux"
 
 SRC_URI="
 	https://github.com/${MyPN}/${MyPN}/archive/${BITCOINCORE_COMMITHASH}.tar.gz -> ${MyPN}-v${PV}.tar.gz


             reply	other threads:[~2018-03-18 13:57 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-18 13:57 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-25 12:04 [gentoo-commits] repo/gentoo:master commit in: dev-util/bitcoin-tx/ Andreas K. Hüttel
2023-10-24  9:14 Joonas Niilola
2023-10-24  9:14 Joonas Niilola
2023-10-19 17:06 Florian Schmaus
2023-03-19  4:21 Sam James
2023-01-06  8:10 Sam James
2023-01-05  6:57 Sam James
2023-01-04 14:28 Arthur Zamarin
2023-01-04 14:28 Arthur Zamarin
2023-01-04  9:42 Sam James
2022-01-15  8:30 Joonas Niilola
2021-12-17  8:13 Florian Schmaus
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:41 Sam James
2021-01-05 20:51 Sam James
2020-12-29  9:47 Sam James
2020-08-19  0:54 Craig Andrews
2020-06-17 13:37 Craig Andrews
2020-06-17  1:52 Craig Andrews
2020-03-07 21:15 Craig Andrews
2020-03-07 21:15 Craig Andrews
2019-08-07 16:33 Craig Andrews
2019-01-11 21:38 Craig Andrews
2018-10-23 20:38 Virgil Dupras
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-18 14:17 Andreas Sturmlechner
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
2017-01-24  1:17 Andreas Sturmlechner
2016-07-01 23:28 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=1521381436.741a0b23542934c0e7c28fedd45ae6686d4ac561.zlogene@gentoo \
    --to=zlogene@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