public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-auth/skey/
Date: Sun, 10 Apr 2016 09:13:35 +0000 (UTC)	[thread overview]
Message-ID: <1460279614.1650c928f7d295ead7eda583abb065dd54783c60.jer@gentoo> (raw)

commit:     1650c928f7d295ead7eda583abb065dd54783c60
Author:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 10 09:13:19 2016 +0000
Commit:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Sun Apr 10 09:13:34 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1650c928

sys-auth/skey: Stable for HPPA (bug #576366).

Package-Manager: portage-2.2.28
RepoMan-Options: --ignore-arches

 sys-auth/skey/skey-1.1.5-r10.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-auth/skey/skey-1.1.5-r10.ebuild b/sys-auth/skey/skey-1.1.5-r10.ebuild
index bc6deb7..b86f069 100644
--- a/sys-auth/skey/skey-1.1.5-r10.ebuild
+++ b/sys-auth/skey/skey-1.1.5-r10.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://gentoo/${P}.tar.bz2
 
 LICENSE="BSD MIT RSA BEER-WARE"
 SLOT="0"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh sparc x86"
+KEYWORDS="~alpha amd64 arm ~arm64 hppa ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh sparc x86"
 IUSE="static-libs"
 
 DEPEND="dev-lang/perl


             reply	other threads:[~2016-04-10  9:13 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-10  9:13 Jeroen Roovers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-04 19:00 [gentoo-commits] repo/gentoo:master commit in: sys-auth/skey/ Ulrich Müller
2023-04-19  7:44 Ulrich Müller
2023-04-19  5:57 Sam James
2023-04-19  5:57 Sam James
2023-04-19  5:57 Sam James
2023-04-19  5:57 Sam James
2023-04-19  5:28 Sam James
2023-04-19  5:28 Sam James
2023-04-19  5:28 Sam James
2023-03-16 21:32 Ulrich Müller
2022-10-20 12:52 Ulrich Müller
2022-10-20 10:56 Jakov Smolić
2022-10-20 10:52 Jakov Smolić
2022-10-20  6:54 Agostino Sarubbo
2022-10-19 17:35 Arthur Zamarin
2022-10-19 17:35 Arthur Zamarin
2022-10-19 17:35 Arthur Zamarin
2022-10-19 17:35 Arthur Zamarin
2022-09-18 23:00 Ulrich Müller
2022-05-07 11:14 WANG Xuerui
2021-06-25 18:31 Ulrich Müller
2021-06-22 21:50 Ulrich Müller
2021-05-25 10:31 Ulrich Müller
2019-05-04 22:04 Mikle Kolyada
2018-06-03 17:45 Mikle Kolyada
2017-02-26 18:26 Ulrich Müller
2017-02-26 17:59 Markus Meier
2017-02-18 14:44 Agostino Sarubbo
2017-02-15 13:49 Tobias Klausmann
2017-02-12 17:01 Agostino Sarubbo
2017-02-12 15:44 Agostino Sarubbo
2017-02-11 13:48 Jeroen Roovers
2017-02-06 14:55 Agostino Sarubbo
2016-10-29 14:56 Ulrich Müller
2016-05-26 22:21 Ulrich Müller
2016-05-26 13:25 Tobias Klausmann
2016-03-25  9:47 Markus Meier
2016-03-19 11:35 Agostino Sarubbo
2016-03-06 12:58 Agostino Sarubbo
2015-12-21 16:43 Ulrich Müller
2015-12-21 14:47 Patrick Lauer
2015-12-13 22:24 Pacho Ramos
2015-12-12 10:19 Ulrich Müller
2015-12-12  9:18 Ulrich Müller
2015-09-24  8:05 Ulrich Müller
2015-09-20  9:30 Agostino Sarubbo
2015-09-06  6:18 Jeroen Roovers
2015-09-02 19:50 Markus Meier
2015-08-30 15:13 Tobias Klausmann
2015-08-26 10:43 Agostino Sarubbo

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=1460279614.1650c928f7d295ead7eda583abb065dd54783c60.jer@gentoo \
    --to=jer@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