public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/capstone/
Date: Wed, 27 Oct 2021 06:35:43 +0000 (UTC)	[thread overview]
Message-ID: <1635316529.7ead496629a43f47d04ea7f5e327baab34087557.ago@gentoo> (raw)

commit:     7ead496629a43f47d04ea7f5e327baab34087557
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 27 06:35:29 2021 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Wed Oct 27 06:35:29 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7ead4966

dev-libs/capstone: amd64 stable wrt bug #815499

Package-Manager: Portage-3.0.20, Repoman-3.0.3
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 dev-libs/capstone/capstone-4.0.2-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/capstone/capstone-4.0.2-r2.ebuild b/dev-libs/capstone/capstone-4.0.2-r2.ebuild
index 893c0616467..b232bd3855b 100644
--- a/dev-libs/capstone/capstone-4.0.2-r2.ebuild
+++ b/dev-libs/capstone/capstone-4.0.2-r2.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://github.com/aquynh/${PN}/archive/${PV/_rc/-rc}.tar.gz -> ${P}.ta
 
 LICENSE="BSD"
 SLOT="0/4" # libcapstone.so.4
-KEYWORDS="~amd64 ~arm ~arm64 ~x86"
+KEYWORDS="amd64 ~arm ~arm64 ~x86"
 
 # A few disassembly outputs need an update
 RESTRICT="test"


             reply	other threads:[~2021-10-27  6:35 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27  6:35 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-02 12:46 [gentoo-commits] repo/gentoo:master commit in: dev-libs/capstone/ Joonas Niilola
2024-10-05  7:54 Arthur Zamarin
2024-10-05  7:39 Michał Górny
2024-08-28  6:39 Joonas Niilola
2024-08-28  6:39 Joonas Niilola
2024-07-03  5:17 Ionen Wolkens
2024-06-02  0:41 Sam James
2024-06-02  0:41 Sam James
2024-01-03  6:22 Sam James
2023-10-04 21:56 Conrad Kostecki
2023-09-26 18:25 Sam James
2023-09-26 17:58 Sam James
2023-09-03 16:39 Sam James
2023-09-03 16:39 Sam James
2023-08-26  4:01 Sam James
2023-08-26  4:01 Sam James
2023-07-31  8:08 Joonas Niilola
2023-07-31  8:08 Joonas Niilola
2023-06-18 19:02 John Helmert III
2023-06-18 19:02 John Helmert III
2023-03-20 21:52 Sam James
2023-03-20 21:52 Sam James
2023-02-17 17:27 Viorel Munteanu
2023-01-20  0:03 Mike Frysinger
2023-01-14  8:04 Arthur Zamarin
2023-01-05  5:21 Sam James
2022-12-02 10:20 WANG Xuerui
2022-12-02 10:20 WANG Xuerui
2022-11-11  6:30 Sam James
2022-11-11  4:25 Sam James
2022-08-27  8:27 Sam James
2022-08-27  8:27 Sam James
2022-08-15 23:10 Sam James
2022-08-15 23:10 Sam James
2022-08-15 23:10 Sam James
2022-08-15 23:10 Sam James
2022-08-15 23:10 Sam James
2022-08-05  7:17 Joonas Niilola
2022-04-29  9:01 Joonas Niilola
2022-04-29  9:01 Joonas Niilola
2022-01-23  8:05 Yixun Lan
2021-10-27  6:37 Agostino Sarubbo
2021-07-23  7:33 Sergei Trofimovich
2021-07-03  7:09 Sergei Trofimovich
2021-05-15 13:58 Sergei Trofimovich
2020-11-10 23:49 Sergei Trofimovich
2020-09-01 18:13 Sergei Trofimovich
2020-09-01 18:13 Sergei Trofimovich
2020-07-05 10:56 Sergei Trofimovich
2020-05-29 22:13 Sergei Trofimovich
2020-05-20 17:53 Sergei Trofimovich
2020-05-08 18:44 Sergei Trofimovich
2020-03-23 23:58 Sergei Trofimovich
2020-02-12 22:32 Sergei Trofimovich
2019-10-02 17:53 Mike Auty
2019-09-18 22:12 Sergei Trofimovich
2019-08-05 12:41 Guilherme Amadio
2019-01-10 21:37 Sergei Trofimovich
2017-12-24 14:13 Sergei Trofimovich
2017-10-12 11:14 Sergei Trofimovich
2017-09-25 13:37 Pacho Ramos
2017-07-29  9:26 Sergei Trofimovich
2017-03-25 16:09 Sergei Trofimovich
2016-09-28 19:26 Richard Farina
2016-09-03 14:01 Sergei Trofimovich
2016-06-04 12:01 Sergei Trofimovich
2016-06-04 11:54 Sergei Trofimovich

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=1635316529.7ead496629a43f47d04ea7f5e327baab34087557.ago@gentoo \
    --to=ago@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