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: net-libs/rabbitmq-c/
Date: Tue, 24 Dec 2019 14:48:12 +0000 (UTC)	[thread overview]
Message-ID: <1577198889.b32fc95a89f9a1fa2d2f6888d19de8b964dc62ac.zlogene@gentoo> (raw)

commit:     b32fc95a89f9a1fa2d2f6888d19de8b964dc62ac
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 24 14:47:52 2019 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Tue Dec 24 14:48:09 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b32fc95a

net-libs/rabbitmq-c: arm stable wrt bug #701810

Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="arm"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>

 net-libs/rabbitmq-c/rabbitmq-c-0.10.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-libs/rabbitmq-c/rabbitmq-c-0.10.0.ebuild b/net-libs/rabbitmq-c/rabbitmq-c-0.10.0.ebuild
index 91110cbd2ae..d8c82ef94e1 100644
--- a/net-libs/rabbitmq-c/rabbitmq-c-0.10.0.ebuild
+++ b/net-libs/rabbitmq-c/rabbitmq-c-0.10.0.ebuild
@@ -13,7 +13,7 @@ if [[ ${PV} == *9999* ]]; then
 	EGIT_REPO_URI="https://github.com/alanxz/${PN}.git"
 else
 	SRC_URI="https://github.com/alanxz/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
-	KEYWORDS="~alpha amd64 ~arm arm64 hppa ia64 ppc ppc64 ~s390 sparc x86"
+	KEYWORDS="~alpha amd64 arm arm64 hppa ia64 ppc ppc64 ~s390 sparc x86"
 fi
 
 LICENSE="MIT"


             reply	other threads:[~2019-12-24 14:48 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24 14:48 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-26 20:00 [gentoo-commits] repo/gentoo:master commit in: net-libs/rabbitmq-c/ Andreas Sturmlechner
2024-03-01  7:28 Viorel Munteanu
2024-03-01  7:28 Viorel Munteanu
2024-03-01  7:28 Viorel Munteanu
2024-03-01  7:28 Viorel Munteanu
2024-02-14 16:48 Sam James
2024-02-13  8:05 Joonas Niilola
2024-02-13  8:05 Joonas Niilola
2024-01-11 14:06 Joonas Niilola
2022-12-04  9:23 WANG Xuerui
2021-11-09 21:33 Sam James
2021-11-09 21:33 Sam James
2021-11-09 21:24 Jakov Smolić
2021-10-27  6:59 Sam James
2021-10-26  3:14 Sam James
2021-10-25 13:11 Sam James
2021-10-25  6:06 Sam James
2021-09-13  0:36 Sam James
2021-07-26 15:45 Marek Szuba
2021-05-02 10:56 Mikle Kolyada
2021-04-12  1:09 Sam James
2019-12-26 15:15 Thomas Deutschmann
2019-12-13  0:07 Thomas Deutschmann
2019-12-10 10:54 Agostino Sarubbo
2019-12-08 10:58 Sergei Trofimovich
2019-12-03 11:58 Agostino Sarubbo
2019-12-03 11:56 Agostino Sarubbo
2019-12-03 10:07 Agostino Sarubbo
2019-12-03 10:03 Agostino Sarubbo
2019-12-03  4:23 Aaron Bauman
2019-12-02 22:03 Thomas Deutschmann
2019-03-03 11:13 Mikle Kolyada
2019-02-23  9:43 Pacho Ramos
2019-02-22 22:03 Mart Raudsepp
2019-02-21 20:28 Markus Meier
2019-02-07 12:57 Mikle Kolyada
2019-02-02 21:17 Sergei Trofimovich
2019-02-02 20:44 Sergei Trofimovich
2019-02-02 19:18 Sergei Trofimovich
2019-02-01  7:17 Sergei Trofimovich
2019-01-31 22:15 Thomas Deutschmann
2019-01-30  8:13 Sergei Trofimovich
2018-12-21 20:16 Sergei Trofimovich
2018-12-19 14:10 Thomas Deutschmann
2018-10-09 14:38 Matt Turner
2018-10-09 14:38 Matt Turner
2018-07-29 10:35 Sergei Trofimovich
2018-06-28 13:48 Mart Raudsepp
2018-06-06 14:55 Andreas Sturmlechner
2018-03-18 13:03 Sergei Trofimovich
2018-03-18 12:36 Sergei Trofimovich
2018-03-17 13:02 Sergei Trofimovich
2018-03-17 13:00 Sergei Trofimovich
2017-08-05 19:04 Sergei Trofimovich
2017-06-21  8:59 Alexis Ballier
2017-03-01  7:55 Michael Weber
2016-12-21 17:14 Thomas Deutschmann
2016-10-01 13:04 Jeroen Roovers
2016-07-07 19:48 Austin English
2016-05-23 13:31 Brian Evans
2016-05-21 15:47 Pacho Ramos
2016-05-21 15:47 Pacho Ramos

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=1577198889.b32fc95a89f9a1fa2d2f6888d19de8b964dc62ac.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