From: "Jason Zaman" <perfinion@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-libs/libsepol/
Date: Sat, 23 Sep 2017 02:15:27 +0000 (UTC) [thread overview]
Message-ID: <1506132744.4a9e3081ef67a9151408f19637a11a1ed439727c.perfinion@gentoo> (raw)
commit: 4a9e3081ef67a9151408f19637a11a1ed439727c
Author: Jason Zaman <perfinion <AT> gentoo <DOT> org>
AuthorDate: Fri Sep 22 15:31:56 2017 +0000
Commit: Jason Zaman <perfinion <AT> gentoo <DOT> org>
CommitDate: Sat Sep 23 02:12:24 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4a9e3081
sys-libs/libsepol: stablize 2.7
Package-Manager: Portage-2.3.8, Repoman-2.3.1
sys-libs/libsepol/libsepol-2.7.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-libs/libsepol/libsepol-2.7.ebuild b/sys-libs/libsepol/libsepol-2.7.ebuild
index e68451424fc..9b566349dc0 100644
--- a/sys-libs/libsepol/libsepol-2.7.ebuild
+++ b/sys-libs/libsepol/libsepol-2.7.ebuild
@@ -17,7 +17,7 @@ if [[ ${PV} == 9999 ]]; then
S="${WORKDIR}/${MY_P}/${PN}"
else
SRC_URI="https://raw.githubusercontent.com/wiki/SELinuxProject/selinux/files/releases/${MY_RELEASEDATE}/${MY_P}.tar.gz"
- KEYWORDS="~amd64 ~arm ~arm64 ~mips ~x86"
+ KEYWORDS="amd64 ~arm ~arm64 ~mips x86"
S="${WORKDIR}/${MY_P}"
fi
next reply other threads:[~2017-09-23 2:15 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 2:15 Jason Zaman [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-06 12:37 [gentoo-commits] repo/gentoo:master commit in: sys-libs/libsepol/ Sam James
2025-05-06 12:37 Sam James
2025-03-09 22:01 Jason Zaman
2025-03-09 22:01 Jason Zaman
2025-02-09 22:45 Jason Zaman
2024-10-31 13:51 Sam James
2024-10-30 17:24 Arthur Zamarin
2024-10-30 15:11 Sam James
2024-10-30 15:11 Sam James
2024-08-12 1:23 Jason Zaman
2024-07-19 19:23 James Le Cuirot
2024-07-19 9:57 James Le Cuirot
2024-07-19 9:57 James Le Cuirot
2024-06-30 0:49 Jason Zaman
2024-06-30 0:36 Jason Zaman
2024-02-09 14:41 Kenton Groombridge
2024-01-17 1:33 Kenton Groombridge
2024-01-17 1:33 Kenton Groombridge
2023-04-15 15:13 Kenton Groombridge
2023-04-09 15:14 Kenton Groombridge
2023-03-30 0:09 Kenton Groombridge
2023-03-30 0:09 Kenton Groombridge
2022-07-18 12:49 Sam James
2022-07-18 12:49 Sam James
2022-07-02 17:03 Kenton Groombridge
2022-06-04 1:03 Kenton Groombridge
2022-06-04 1:03 Kenton Groombridge
2022-04-11 4:59 Jason Zaman
2022-04-11 3:44 Jason Zaman
2022-04-09 2:55 Jason Zaman
2021-12-28 1:14 Jason Zaman
2021-11-20 23:20 Sam James
2021-11-20 23:20 Sam James
2021-10-31 2:55 Sam James
2021-07-28 20:08 Sam James
2021-07-04 22:19 Sam James
2021-04-03 4:19 Jason Zaman
2021-04-03 4:19 Jason Zaman
2020-12-18 3:31 Jason Zaman
2020-12-03 3:12 Jason Zaman
2020-09-15 3:41 Jason Zaman
2020-07-01 17:34 Mike Gilbert
2020-02-11 19:50 Agostino Sarubbo
2020-02-11 19:43 Agostino Sarubbo
2019-12-08 18:39 Jason Zaman
2019-12-08 17:26 Jason Zaman
2019-12-08 17:26 Jason Zaman
2019-12-02 14:50 Jason Zaman
2019-08-17 10:09 Jason Zaman
2019-08-17 10:09 Jason Zaman
2019-03-31 13:46 Jason Zaman
2019-03-31 13:46 Jason Zaman
2019-02-09 11:49 Jason Zaman
2019-02-09 11:49 Jason Zaman
2018-06-26 2:07 Jason Zaman
2018-05-25 7:29 Jason Zaman
2018-05-25 7:29 Jason Zaman
2018-05-13 17:28 Jason Zaman
2018-05-13 17:28 Jason Zaman
2018-04-27 4:45 Jason Zaman
2018-04-27 4:45 Jason Zaman
2018-04-26 11:22 Jason Zaman
2018-04-26 11:22 Jason Zaman
2017-09-23 2:15 Jason Zaman
2017-08-07 16:48 Jason Zaman
2017-08-07 16:48 Jason Zaman
2017-07-22 11:08 Jason Zaman
2017-07-22 11:08 Jason Zaman
2017-07-09 10:03 Jason Zaman
2017-07-09 10:03 Jason Zaman
2017-06-13 15:20 Jason Zaman
2017-06-13 15:20 Jason Zaman
2016-12-12 14:01 Jason Zaman
2016-10-24 15:39 Jason Zaman
2016-10-07 4:24 Jason Zaman
2016-10-03 7:30 Jason Zaman
2016-09-01 16:31 Jason Zaman
2016-08-07 17:07 Jason Zaman
2016-06-01 14:15 Jason Zaman
2016-03-13 19:47 Sven Vermeulen
2015-12-21 8:57 Jason Zaman
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=1506132744.4a9e3081ef67a9151408f19637a11a1ed439727c.perfinion@gentoo \
--to=perfinion@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