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: sys-apps/keyutils/
Date: Sun, 22 Sep 2019 09:32:04 +0000 (UTC)	[thread overview]
Message-ID: <1569144713.6beb193b280b25aa4a8d8e756dcbf3a6e4aa643b.ago@gentoo> (raw)

commit:     6beb193b280b25aa4a8d8e756dcbf3a6e4aa643b
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 22 09:31:53 2019 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sun Sep 22 09:31:53 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6beb193b

sys-apps/keyutils: ia64 stable wrt bug #693240

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

 sys-apps/keyutils/keyutils-1.6.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-apps/keyutils/keyutils-1.6.1.ebuild b/sys-apps/keyutils/keyutils-1.6.1.ebuild
index bc739bc0146..d68746b5022 100644
--- a/sys-apps/keyutils/keyutils-1.6.1.ebuild
+++ b/sys-apps/keyutils/keyutils-1.6.1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/s
 
 LICENSE="GPL-2 LGPL-2.1"
 SLOT="0/1.9"
-KEYWORDS="alpha amd64 arm arm64 ~hppa ~ia64 ~m68k ~mips ppc ppc64 ~riscv ~s390 ~sh sparc x86 ~amd64-linux ~x86-linux"
+KEYWORDS="alpha amd64 arm arm64 ~hppa ia64 ~m68k ~mips ppc ppc64 ~riscv ~s390 ~sh sparc x86 ~amd64-linux ~x86-linux"
 IUSE="static static-libs test"
 
 RDEPEND=""


             reply	other threads:[~2019-09-22  9:32 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-22  9:32 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-15  0:12 [gentoo-commits] repo/gentoo:master commit in: sys-apps/keyutils/ Mike Gilbert
2024-03-03  4:00 Sam James
2024-03-02 12:12 Arthur Zamarin
2024-03-02 12:12 Arthur Zamarin
2024-03-02 12:12 Arthur Zamarin
2024-03-02 12:12 Arthur Zamarin
2024-03-02 12:12 Arthur Zamarin
2024-03-02 12:12 Arthur Zamarin
2024-02-07 19:20 Sam James
2024-01-05 14:02 Sam James
2024-01-05 14:02 Sam James
2023-10-10  4:34 Sam James
2023-04-06  5:18 Sam James
2023-04-06  4:50 Sam James
2022-12-26  8:35 Sam James
2022-11-22  8:04 Arthur Zamarin
2022-10-29 14:45 Sam James
2022-05-11  0:49 Sam James
2022-05-11  0:49 Sam James
2022-05-10 14:34 Agostino Sarubbo
2022-05-10 13:47 Agostino Sarubbo
2022-05-10 13:47 Agostino Sarubbo
2022-04-27 18:06 Arthur Zamarin
2022-01-14 14:42 Arthur Zamarin
2022-01-13  2:56 Georgy Yakovlev
2021-05-13 16:15 Sam James
2021-05-13 13:55 David Seifert
2020-07-08 11:34 Thomas Deutschmann
2020-07-07 17:08 Thomas Deutschmann
2020-01-06 11:52 Mike Frysinger
2019-11-02  0:23 Sergei Trofimovich
2019-09-21  5:20 Matt Turner
2019-09-16  7:55 Agostino Sarubbo
2019-09-13 18:01 Mikle Kolyada
2019-09-11  8:43 Agostino Sarubbo
2019-09-11  8:41 Agostino Sarubbo
2019-09-11  8:28 Agostino Sarubbo
2019-09-11  8:20 Agostino Sarubbo
2019-09-09 17:20 Aaron Bauman
2019-05-05 12:06 Mikle Kolyada
2018-11-16 12:53 Lars Wendler
2018-09-01  1:32 Thomas Deutschmann
2018-08-31 14:55 Thomas Deutschmann
2018-08-31 14:55 Thomas Deutschmann
2018-08-31 14:55 Thomas Deutschmann
2018-08-31 14:55 Thomas Deutschmann
2018-08-31  2:54 Thomas Deutschmann
2018-08-02 15:50 Lars Wendler
2018-03-11  6:24 Matt Turner
2018-03-11  1:12 Matt Turner
2018-02-18 12:28 Tobias Klausmann
2018-01-24 21:25 Sergei Trofimovich
2018-01-12  4:10 Mike Frysinger
2018-01-09  8:09 Sergei Trofimovich
2018-01-04 15:42 Lars Wendler
2018-01-04 15:25 Lars Wendler
2017-05-24 16:30 Lars Wendler
2017-03-14 21:03 Mike Frysinger
2016-04-18 19:10 Mike Frysinger
2016-03-30 23:48 Mike Frysinger
2016-03-30 23:48 Mike Frysinger

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=1569144713.6beb193b280b25aa4a8d8e756dcbf3a6e4aa643b.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