public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/libnsl/
Date: Sun, 12 Nov 2017 14:16:41 +0000 (UTC)	[thread overview]
Message-ID: <1510496128.6e3b9524bc74f258b30dd22a4f1e6612e45843b6.dilfridge@gentoo> (raw)

commit:     6e3b9524bc74f258b30dd22a4f1e6612e45843b6
Author:     Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 12 12:30:13 2017 +0000
Commit:     Andreas Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Sun Nov 12 14:15:28 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6e3b9524

net-libs/libnsl: Keyword for all arches

This is essentially code split off from glibc.

Package-Manager: Portage-2.3.13, Repoman-2.3.4

 net-libs/libnsl/libnsl-1.1.0-r1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/net-libs/libnsl/libnsl-1.1.0-r1.ebuild b/net-libs/libnsl/libnsl-1.1.0-r1.ebuild
index 407fc963fda..13f9c3fbadf 100644
--- a/net-libs/libnsl/libnsl-1.1.0-r1.ebuild
+++ b/net-libs/libnsl/libnsl-1.1.0-r1.ebuild
@@ -12,8 +12,8 @@ SRC_URI="https://github.com/thkukuk/${PN}/archive/${P}.tar.gz"
 SLOT="0/2"
 LICENSE="LGPL-2.1+"
 
-# Restore keywords and stabilize together with glibc-2.26!
-KEYWORDS=""
+# Stabilize together with glibc-2.26!
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86"
 
 IUSE=""
 


             reply	other threads:[~2017-11-12 14:16 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-12 14:16 Andreas Hüttel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-23  4:17 [gentoo-commits] repo/gentoo:master commit in: net-libs/libnsl/ Ionen Wolkens
2023-12-15 13:21 Arthur Zamarin
2023-12-15 10:53 Arthur Zamarin
2023-12-15 10:38 Arthur Zamarin
2023-12-15  7:49 Sam James
2023-12-15  7:14 Sam James
2023-12-15  7:14 Sam James
2023-12-15  7:14 Sam James
2023-10-13 15:00 Sam James
2023-08-20 20:28 Andreas K. Hüttel
2022-10-29 12:08 Sam James
2022-06-14  8:15 Jakov Smolić
2022-06-14  8:15 Jakov Smolić
2022-06-14  6:39 Jakov Smolić
2022-06-14  6:18 Jakov Smolić
2022-06-14  5:54 Jakov Smolić
2022-06-13 21:50 Jakov Smolić
2022-06-13 21:50 Jakov Smolić
2022-06-13 21:13 Sam James
2021-09-19  1:00 Sam James
2021-08-18  8:04 Lars Wendler
2021-08-14  3:48 Sam James
2021-05-24 15:09 Mike Gilbert
2020-09-12  9:00 Sergei Trofimovich
2020-08-31  0:42 Sam James
2020-08-17  0:20 Robin H. Johnson
2020-08-11 19:11 Sergei Trofimovich
2020-08-11 16:18 Sam James
2020-08-11 14:23 Agostino Sarubbo
2020-08-11 14:13 Agostino Sarubbo
2020-08-10 19:25 Sergei Trofimovich
2020-08-10 12:04 Agostino Sarubbo
2020-08-10  9:30 Agostino Sarubbo
2020-07-11 12:58 Sergei Trofimovich
2020-07-08 22:34 Lars Wendler
2020-07-06 18:21 Lars Wendler
2020-03-23 23:58 Sergei Trofimovich
2019-05-04 19:40 Andreas K. Hüttel
2018-11-14 16:22 Robin H. Johnson
2018-09-05 19:31 Anthony G. Basile
2018-09-05 15:36 Anthony G. Basile
2018-08-26  8:10 Jeroen Roovers
2018-07-02 18:27 Markus Meier
2018-06-25 16:06 Tobias Klausmann
2018-06-23  8:24 Sergei Trofimovich
2018-06-06 15:25 Thomas Deutschmann
2018-06-05 17:51 Mike Frysinger
2018-06-05 17:25 Mart Raudsepp
2018-06-02 21:48 Sergei Trofimovich
2018-06-02 19:28 Andreas Hüttel
2018-04-30 11:26 Andreas Hüttel
2018-01-22 16:19 Michael Haubenwallner
2018-01-12  4:10 Mike Frysinger
2017-11-23 20:48 Thomas Deutschmann
2017-11-21 19:13 Mike Gilbert
2017-11-21 19:11 Mike Gilbert
2017-11-21 19:11 Mike Gilbert
2017-11-06  0:43 Anthony G. Basile
2017-11-01 11:48 Andreas Hüttel
2017-10-28 18:56 Andreas Hüttel
2017-10-28 18:28 Andreas Hüttel
2017-09-18 11:50 Michael Haubenwallner
2017-09-16 17:25 Sergei Trofimovich
2017-09-16 15:48 Andreas Hüttel
2017-09-07 20:29 Andreas Hüttel

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=1510496128.6e3b9524bc74f258b30dd22a4f1e6612e45843b6.dilfridge@gentoo \
    --to=dilfridge@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