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: net-libs/libnma/
Date: Mon, 17 Aug 2020 13:50:31 +0000 (UTC)	[thread overview]
Message-ID: <1597672227.6ff45b63d8b04dc98a4fb3d864979b4bb1ccf68e.ago@gentoo> (raw)

commit:     6ff45b63d8b04dc98a4fb3d864979b4bb1ccf68e
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 17 13:49:24 2020 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Mon Aug 17 13:50:27 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6ff45b63

net-libs/libnma: amd64 stable wrt bug #737294

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

 net-libs/libnma/libnma-1.8.30.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-libs/libnma/libnma-1.8.30.ebuild b/net-libs/libnma/libnma-1.8.30.ebuild
index f2b65621559..fed0d7b6379 100644
--- a/net-libs/libnma/libnma-1.8.30.ebuild
+++ b/net-libs/libnma/libnma-1.8.30.ebuild
@@ -13,7 +13,7 @@ SLOT="0"
 # pkcs11 default enabled as it's a small dep often already present by libnma users, and it was default enabled as IUSE=+gcr in nm-applet before
 IUSE="gtk-doc +introspection +pkcs11 vala"
 REQUIRED_USE="vala? ( introspection )"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~sparc x86"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~sparc x86"
 
 DEPEND="
 	app-text/iso-codes


             reply	other threads:[~2020-08-17 13:50 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 13:50 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-20 10:16 [gentoo-commits] repo/gentoo:master commit in: net-libs/libnma/ WANG Xuerui
2023-03-30  8:59 David Seifert
2023-02-17  8:23 Arthur Zamarin
2023-02-16 18:39 Arthur Zamarin
2023-02-16 18:39 Arthur Zamarin
2023-01-09 15:45 Matt Turner
2023-01-03 14:08 Matt Turner
2022-12-22 11:13 Arthur Zamarin
2022-12-17  6:45 Arthur Zamarin
2022-12-16 20:57 Arthur Zamarin
2022-12-04 14:50 Pacho Ramos
2022-12-04  2:41 Matt Turner
2022-11-10 15:41 Matt Turner
2022-11-05  9:58 Arthur Zamarin
2022-11-05  9:44 Arthur Zamarin
2022-10-31 14:28 Matt Turner
2022-10-06 16:38 Matt Turner
2022-10-01 17:16 Matt Turner
2022-07-21  2:04 Matt Turner
2022-07-21  0:13 Sam James
2022-07-18 23:41 Sam James
2022-07-18 17:44 Sam James
2022-06-15 18:31 Matt Turner
2022-05-31 18:04 Matt Turner
2022-05-31  9:24 Jakov Smolić
2022-05-28  5:05 Sam James
2022-05-15  3:10 Sam James
2022-05-10  4:06 Arthur Zamarin
2022-05-07 18:28 Arthur Zamarin
2022-04-18 20:48 Jakov Smolić
2022-04-08 21:21 Matt Turner
2022-03-25 20:54 Matt Turner
2022-03-09 15:39 Sam James
2022-03-09 12:49 Sam James
2022-01-24 22:43 Matt Turner
2022-01-19 17:30 Matt Turner
2021-11-06  4:09 Sam James
2021-11-06  3:58 Sam James
2021-10-04  1:25 Sam James
2021-10-04  1:24 Sam James
2021-08-27 15:19 Yixun Lan
2021-08-20 20:25 Matt Turner
2020-09-24  6:52 Agostino Sarubbo
2020-09-06 22:04 Sam James
2020-08-17 10:01 Agostino Sarubbo
2020-06-27 21:03 Mart Raudsepp
2020-04-19 15:37 Mart Raudsepp

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=1597672227.6ff45b63d8b04dc98a4fb3d864979b4bb1ccf68e.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