From: "Alexis Ballier" <aballier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-base/libgtop/
Date: Mon, 19 Jun 2017 11:42:43 +0000 (UTC) [thread overview]
Message-ID: <1497871018.829a308b99f34ef66bad5d32b567f5b2b8d7b2d9.aballier@gentoo> (raw)
commit: 829a308b99f34ef66bad5d32b567f5b2b8d7b2d9
Author: Alexis Ballier <aballier <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 19 11:16:58 2017 +0000
Commit: Alexis Ballier <aballier <AT> gentoo <DOT> org>
CommitDate: Mon Jun 19 11:16:58 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=829a308b
gnome-base/libgtop: keyword ~arm64
Package-Manager: Portage-2.3.6, Repoman-2.3.2
gnome-base/libgtop/libgtop-2.34.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnome-base/libgtop/libgtop-2.34.2.ebuild b/gnome-base/libgtop/libgtop-2.34.2.ebuild
index fa964239165..acafa2277c4 100644
--- a/gnome-base/libgtop/libgtop-2.34.2.ebuild
+++ b/gnome-base/libgtop/libgtop-2.34.2.ebuild
@@ -9,7 +9,7 @@ HOMEPAGE="https://git.gnome.org/browse/libgtop"
LICENSE="GPL-2"
SLOT="2/10" # libgtop soname version
-KEYWORDS="alpha amd64 arm ia64 ~mips ppc ppc64 ~sh sparc x86 ~x86-fbsd"
+KEYWORDS="alpha amd64 arm ~arm64 ia64 ~mips ppc ppc64 ~sh sparc x86 ~x86-fbsd"
IUSE="+introspection"
RDEPEND="
next reply other threads:[~2017-06-19 11:42 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 11:42 Alexis Ballier [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-01 8:10 [gentoo-commits] repo/gentoo:master commit in: gnome-base/libgtop/ Pacho Ramos
2022-12-22 11:13 Arthur Zamarin
2022-12-17 6:45 Arthur Zamarin
2022-12-16 20:57 Arthur Zamarin
2022-12-16 20:30 Arthur Zamarin
2022-10-30 16:34 Matt Turner
2021-05-21 14:54 Yixun Lan
2021-02-15 8:38 Sam James
2021-01-18 21:10 Matt Turner
2020-06-17 20:45 Mart Raudsepp
2020-06-16 16:41 Sergei Trofimovich
2020-04-22 14:25 Agostino Sarubbo
2020-04-22 8:44 Agostino Sarubbo
2020-04-22 8:41 Agostino Sarubbo
2020-04-20 20:42 Mart Raudsepp
2020-04-11 15:57 Sergei Trofimovich
2020-04-11 15:57 Sergei Trofimovich
2020-02-22 11:52 Mart Raudsepp
2020-01-11 20:01 Mart Raudsepp
2020-01-11 20:01 Mart Raudsepp
2019-07-03 7:11 Agostino Sarubbo
2019-06-27 12:35 Agostino Sarubbo
2019-06-17 19:40 Sergei Trofimovich
2019-06-17 10:07 Mikle Kolyada
2019-05-23 13:02 Mikle Kolyada
2018-08-02 5:50 Mart Raudsepp
2018-08-02 5:50 Mart Raudsepp
2018-03-15 1:50 Mart Raudsepp
2018-03-14 21:41 Sergei Trofimovich
2018-03-14 21:09 Markus Meier
2018-03-06 21:37 Tobias Klausmann
2018-03-04 20:48 Sergei Trofimovich
2018-02-16 20:39 Sergei Trofimovich
2018-01-18 3:42 Mikle Kolyada
2018-01-13 12:13 Sergei Trofimovich
2017-09-01 7:00 Gilles Dartiguelongue
2017-08-15 22:44 Gilles Dartiguelongue
2017-02-24 23:04 Mart Raudsepp
2017-02-24 21:29 Michael Weber
2017-02-24 14:07 Agostino Sarubbo
2017-02-21 9:16 Tobias Klausmann
2017-02-18 14:44 Agostino Sarubbo
2017-02-17 10:56 Agostino Sarubbo
2017-01-21 19:51 Pacho Ramos
2017-01-21 19:51 Pacho Ramos
2016-12-06 20:32 Markus Meier
2016-09-08 7:26 Gilles Dartiguelongue
2016-06-07 7:03 Tobias Klausmann
2016-05-03 20:17 Markus Meier
2016-03-06 18:20 Mikle Kolyada
2015-11-26 10:51 Gilles Dartiguelongue
2015-11-14 19:46 Pacho Ramos
2015-11-14 19:46 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=1497871018.829a308b99f34ef66bad5d32b567f5b2b8d7b2d9.aballier@gentoo \
--to=aballier@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