From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/features/selinux/
Date: Sat, 5 Dec 2015 11:23:22 +0000 (UTC) [thread overview]
Message-ID: <1449314600.fab5276bc2fb517df5dfd8752e63af7dace477ce.jlec@gentoo> (raw)
commit: fab5276bc2fb517df5dfd8752e63af7dace477ce
Author: Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 5 11:21:42 2015 +0000
Commit: Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Sat Dec 5 11:23:20 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fab5276b
profiles: Mask pypy support for app-portage/flaggie on selinux
Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=567450
Signed-off-by: Justin Lecher <jlec <AT> gentoo.org>
profiles/features/selinux/package.use.mask | 1 +
1 file changed, 1 insertion(+)
diff --git a/profiles/features/selinux/package.use.mask b/profiles/features/selinux/package.use.mask
index 0c3be43..429738c 100644
--- a/profiles/features/selinux/package.use.mask
+++ b/profiles/features/selinux/package.use.mask
@@ -13,6 +13,7 @@ app-portage/gentoolkit python_targets_pypy python_targets_pypy3
app-portage/layman python_targets_pypy python_targets_pypy3
app-admin/webapp-config python_targets_pypy python_targets_pypy3
app-portage/diffmask python_targets_pypy python_targets_pypy3
+app-portage/flaggie python_targets_pypy python_targets_pypy3
# Jason Zaman <perfinion@gentoo.org> (27 Jun 2015)
# SystemD has no support in the SELinux policy at the moment.
next reply other threads:[~2015-12-05 11:23 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 11:23 Justin Lecher [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-08 22:46 [gentoo-commits] repo/gentoo:master commit in: profiles/features/selinux/ Jason Zaman
2024-12-14 22:47 Jason Zaman
2023-05-01 5:07 Sam James
2022-11-02 17:22 Kenton Groombridge
2022-09-10 4:03 John Helmert III
2022-08-31 22:13 Sam James
2022-08-31 22:13 Sam James
2022-07-18 12:46 Ben Kohler
2022-07-18 12:46 Ben Kohler
2022-06-05 6:56 Sam James
2021-11-22 1:19 Sam James
2021-11-22 1:19 Sam James
2021-11-21 5:30 Sam James
2021-07-09 4:25 Sam James
2021-07-09 1:54 Ionen Wolkens
2021-07-05 20:24 Jason Zaman
2021-07-05 19:53 Jason Zaman
2021-07-05 19:53 Jason Zaman
2021-06-29 6:09 Sam James
2021-06-04 6:20 Georgy Yakovlev
2021-05-20 12:37 Pacho Ramos
2021-05-05 12:19 Michał Górny
2021-04-06 14:15 Andreas Sturmlechner
2021-03-28 10:19 Pacho Ramos
2021-02-01 19:08 Mikle Kolyada
2021-02-01 8:01 Sam James
2021-02-01 8:01 Sam James
2021-02-01 8:01 Sam James
2021-02-01 8:01 Sam James
2021-02-01 8:01 Sam James
2020-12-14 16:30 Ben Kohler
2020-10-25 21:29 Jason Zaman
2020-10-22 5:18 Georgy Yakovlev
2020-10-07 10:17 Georgy Yakovlev
2020-10-07 9:55 Georgy Yakovlev
2020-09-16 11:05 Ben Kohler
2020-08-30 10:01 Pacho Ramos
2020-08-21 13:00 Pacho Ramos
2020-05-05 7:24 Joonas Niilola
2020-04-02 18:56 Pacho Ramos
2020-03-29 2:49 Jason Zaman
2020-03-15 17:54 Pacho Ramos
2020-02-09 15:54 Michał Górny
2019-11-02 11:50 James Le Cuirot
2019-10-15 15:53 Matthew Thode
2019-10-15 13:17 Andreas Sturmlechner
2019-04-20 17:59 Pacho Ramos
2019-04-13 15:58 Pacho Ramos
2019-03-24 16:44 Pacho Ramos
2019-03-24 15:34 Pacho Ramos
2019-03-19 9:03 Jason Zaman
2018-07-30 17:04 Matt Thode
2018-07-24 16:08 Pacho Ramos
2018-06-23 8:09 Pacho Ramos
2018-05-23 23:27 Gilles Dartiguelongue
2018-05-08 16:52 Michał Górny
2018-04-02 11:27 Mart Raudsepp
2018-02-13 21:30 Pacho Ramos
2018-01-09 17:58 Jason Zaman
2017-12-30 10:16 Michał Górny
2017-09-11 2:57 Mike Gilbert
2016-12-25 19:27 Johannes Huber
2016-11-12 11:04 Gilles Dartiguelongue
2016-09-15 6:31 Jason Zaman
2015-11-21 10:45 Pacho Ramos
2015-11-21 3:32 Pacho Ramos
2015-11-20 19:39 Pacho Ramos
2015-11-19 21:43 Pacho Ramos
2015-09-06 20:27 Alex Brandt
2015-09-05 13:56 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=1449314600.fab5276bc2fb517df5dfd8752e63af7dace477ce.jlec@gentoo \
--to=jlec@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