public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-libs/nss_wrapper/
Date: Sat,  5 Dec 2020 11:43:44 +0000 (UTC)	[thread overview]
Message-ID: <1607168620.76a413267107dbc40d3f5a26b759da0938cc787b.slyfox@gentoo> (raw)

commit:     76a413267107dbc40d3f5a26b759da0938cc787b
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Dec  5 11:43:13 2020 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Dec  5 11:43:40 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=76a41326

sys-libs/nss_wrapper: stable 1.1.10 for sparc

stable wrt bug #737490

Package-Manager: Portage-3.0.11, Repoman-3.0.2
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>

 sys-libs/nss_wrapper/nss_wrapper-1.1.10.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-libs/nss_wrapper/nss_wrapper-1.1.10.ebuild b/sys-libs/nss_wrapper/nss_wrapper-1.1.10.ebuild
index b412ee829d0..81bca4f18a7 100644
--- a/sys-libs/nss_wrapper/nss_wrapper-1.1.10.ebuild
+++ b/sys-libs/nss_wrapper/nss_wrapper-1.1.10.ebuild
@@ -12,4 +12,4 @@ SRC_URI="https://ftp.samba.org/pub/cwrap/${P}.tar.gz"
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 arm arm64 ~hppa ~ia64 ppc ppc64 ~sparc x86"
+KEYWORDS="~alpha ~amd64 arm arm64 ~hppa ~ia64 ppc ppc64 sparc x86"


             reply	other threads:[~2020-12-05 11:43 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 11:43 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-03  6:08 [gentoo-commits] repo/gentoo:master commit in: sys-libs/nss_wrapper/ Sam James
2023-11-24  9:31 Sam James
2023-04-01 16:32 Arthur Zamarin
2023-04-01 16:32 Arthur Zamarin
2023-04-01 16:32 Arthur Zamarin
2023-03-16 17:38 Arthur Zamarin
2023-02-26 19:10 Arthur Zamarin
2023-02-23 20:47 Arthur Zamarin
2023-02-23 20:04 Arthur Zamarin
2023-01-28 23:21 Andreas Sturmlechner
2022-09-30  3:11 Sam James
2022-08-31  7:37 Jakov Smolić
2022-08-31  7:37 Jakov Smolić
2022-08-31  5:12 Arthur Zamarin
2022-08-30 22:55 Sam James
2022-08-30 22:52 Sam James
2022-08-30 22:51 Sam James
2022-08-30 22:51 Sam James
2022-08-03 23:33 Sam James
2022-07-30 16:40 Ben Kohler
2021-07-24 23:02 Marek Szuba
2020-12-17  1:01 Sam James
2020-12-04 18:37 Sergei Trofimovich
2020-12-04 18:31 Sergei Trofimovich
2020-12-02 21:29 Sam James
2020-12-02 10:23 Sam James
2020-12-02  3:06 Thomas Deutschmann
2020-05-09  8:47 Mart Raudsepp
2020-03-28 19:01 Andreas Sturmlechner
2020-03-25  8:12 Agostino Sarubbo
2020-03-23 11:05 Agostino Sarubbo
2020-03-23 11:05 Agostino Sarubbo
2020-03-23 11:04 Agostino Sarubbo
2020-03-23 11:04 Agostino Sarubbo
2020-03-23 11:03 Agostino Sarubbo
2020-03-21 20:55 Lars Wendler
2020-03-21 20:55 Lars Wendler
2020-03-21 20:55 Lars Wendler
2020-03-21 14:10 Andreas Sturmlechner
2019-09-26 13:50 Thomas Deutschmann
2018-11-12  9:36 Lars Wendler
2018-08-18 17:03 Andreas Sturmlechner
2016-12-19 10:56 Tobias Klausmann
2016-12-04 16:52 Tobias Klausmann
2016-04-24 20:51 Stephen Klimaszewski
2016-04-23 10:31 Jeroen Roovers
2016-04-11 13:47 Agostino Sarubbo
2016-04-11 13:46 Agostino Sarubbo
2016-04-03 20:11 Steve Arnold
2016-03-31  9:25 Agostino Sarubbo
2016-03-30  8:34 Agostino Sarubbo
2016-03-30  8:30 Agostino Sarubbo
2016-03-29 10:18 Agostino Sarubbo
2016-03-29 10:17 Agostino Sarubbo
2016-03-18 13:34 Lars Wendler
2016-03-18 13:34 Lars Wendler
2015-12-22 12:07 Lars Wendler
2015-12-22 12:07 Lars Wendler
2015-11-26  7:52 Lars Wendler
2015-11-23 11:02 Lars Wendler
2015-11-13  7:07 Jeroen Roovers
2015-08-28 14:14 Lars Wendler
2015-08-28 12:04 Lars Wendler

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=1607168620.76a413267107dbc40d3f5a26b759da0938cc787b.slyfox@gentoo \
    --to=slyfox@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