From: "Sven Vermeulen" <swift@gentoo.org> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] proj/hardened-refpolicy:master commit in: / Date: Sat, 22 Nov 2014 16:25:59 +0000 (UTC) [thread overview] Message-ID: <1416673477.8417dc67710b700fb07902f2061e4e5856a6dfa6.swift@gentoo> (raw) commit: 8417dc67710b700fb07902f2061e4e5856a6dfa6 Author: Nicolas Iooss <nicolas.iooss <AT> m4x <DOT> org> AuthorDate: Mon Nov 10 18:05:29 2014 +0000 Commit: Sven Vermeulen <swift <AT> gentoo <DOT> org> CommitDate: Sat Nov 22 16:24:37 2014 +0000 URL: http://sources.gentoo.org/gitweb/?p=proj/hardened-refpolicy.git;a=commit;h=8417dc67 Update Python requirement in INSTALL PyXML has not been required to build the policy and its documentation since at least Python 2.6, which comes with an "xml" module. Moreover, some support scripts requires Python 2.6 or above (and are compatible with Python 3.4, maybe also with other versions of Python 3). Add the minimum supported version of Python in INSTALL. ML thread: http://oss.tresys.com/pipermail/refpolicy/2014-November/007440.html --- INSTALL | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/INSTALL b/INSTALL index f168ff5..5250cbe 100644 --- a/INSTALL +++ b/INSTALL @@ -3,7 +3,7 @@ Reference Policy has the following build requirements: * libsemanage 2.1.6 * checkpolicy 2.1.8 * policycoreutils 2.1.10 - * Python PyXML + * Python >= 2.6 * GCC To install Reference Policy sources into /etc/selinux/refpolicy/src/policy:
WARNING: multiple messages have this Message-ID (diff)
From: "Sven Vermeulen" <swift@gentoo.org> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] proj/hardened-refpolicy:bitcoin commit in: / Date: Sun, 23 Nov 2014 14:06:10 +0000 (UTC) [thread overview] Message-ID: <1416673477.8417dc67710b700fb07902f2061e4e5856a6dfa6.swift@gentoo> (raw) Message-ID: <20141123140610.greMKxBDc3nkfT_BY_h3ziKI04_wmq8VbKSx23YC-0M@z> (raw) commit: 8417dc67710b700fb07902f2061e4e5856a6dfa6 Author: Nicolas Iooss <nicolas.iooss <AT> m4x <DOT> org> AuthorDate: Mon Nov 10 18:05:29 2014 +0000 Commit: Sven Vermeulen <swift <AT> gentoo <DOT> org> CommitDate: Sat Nov 22 16:24:37 2014 +0000 URL: http://sources.gentoo.org/gitweb/?p=proj/hardened-refpolicy.git;a=commit;h=8417dc67 Update Python requirement in INSTALL PyXML has not been required to build the policy and its documentation since at least Python 2.6, which comes with an "xml" module. Moreover, some support scripts requires Python 2.6 or above (and are compatible with Python 3.4, maybe also with other versions of Python 3). Add the minimum supported version of Python in INSTALL. ML thread: http://oss.tresys.com/pipermail/refpolicy/2014-November/007440.html --- INSTALL | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/INSTALL b/INSTALL index f168ff5..5250cbe 100644 --- a/INSTALL +++ b/INSTALL @@ -3,7 +3,7 @@ Reference Policy has the following build requirements: * libsemanage 2.1.6 * checkpolicy 2.1.8 * policycoreutils 2.1.10 - * Python PyXML + * Python >= 2.6 * GCC To install Reference Policy sources into /etc/selinux/refpolicy/src/policy:
next reply other threads:[~2014-11-22 16:26 UTC|newest] Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-22 16:25 Sven Vermeulen [this message] 2014-11-23 14:06 ` [gentoo-commits] proj/hardened-refpolicy:bitcoin commit in: / Sven Vermeulen -- strict thread matches above, loose matches on Subject: below -- 2025-03-08 23:55 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2025-03-08 23:55 Jason Zaman 2024-09-22 0:03 Jason Zaman 2024-09-22 0:03 Jason Zaman 2024-03-01 19:56 Kenton Groombridge 2024-03-01 19:56 Kenton Groombridge 2024-03-01 19:56 Kenton Groombridge 2024-03-01 19:56 Kenton Groombridge 2024-03-01 19:56 Kenton Groombridge 2023-02-10 20:30 Kenton Groombridge 2022-03-31 3:31 Jason Zaman 2022-03-31 3:31 Jason Zaman 2022-03-31 3:31 Jason Zaman 2022-03-31 3:31 Jason Zaman 2021-11-11 21:27 Jason Zaman 2021-04-03 3:10 Jason Zaman 2021-02-07 3:21 Jason Zaman 2021-02-07 3:20 Jason Zaman 2021-02-07 3:20 Jason Zaman 2021-02-07 3:20 Jason Zaman 2021-02-07 3:20 Jason Zaman 2021-02-07 3:20 Jason Zaman 2021-02-07 3:20 Jason Zaman 2021-02-07 3:20 Jason Zaman 2021-01-11 1:27 Jason Zaman 2020-10-13 3:02 Jason Zaman 2019-12-16 17:48 Jason Zaman 2019-07-13 7:01 Jason Zaman 2019-07-13 7:01 Jason Zaman 2019-02-10 4:14 Jason Zaman 2018-07-08 11:47 Jason Zaman 2018-06-24 8:46 Jason Zaman 2018-03-25 10:29 Sven Vermeulen 2018-01-18 16:37 Sven Vermeulen 2017-06-13 8:25 Jason Zaman 2017-04-10 16:59 Sven Vermeulen 2017-03-30 17:06 Jason Zaman 2017-03-30 17:06 Jason Zaman 2017-03-02 10:17 Sven Vermeulen 2017-02-27 10:50 Jason Zaman 2017-02-25 16:58 Jason Zaman 2017-02-21 7:11 Jason Zaman 2017-02-21 7:11 Jason Zaman 2017-02-05 6:29 Jason Zaman 2017-01-23 15:44 Jason Zaman 2017-01-23 15:44 Jason Zaman 2017-01-23 15:44 Jason Zaman 2017-01-13 18:43 Sven Vermeulen 2017-01-13 18:43 Sven Vermeulen 2017-01-13 18:43 Sven Vermeulen 2016-12-06 13:39 Jason Zaman 2016-10-24 16:02 [gentoo-commits] proj/hardened-refpolicy:swift " Sven Vermeulen 2016-10-24 16:02 ` [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen 2016-10-24 16:02 [gentoo-commits] proj/hardened-refpolicy:swift " Sven Vermeulen 2016-10-24 16:02 ` [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen 2016-10-24 16:02 Sven Vermeulen 2016-08-31 16:38 Jason Zaman 2016-08-31 16:38 Jason Zaman 2016-05-13 5:37 Jason Zaman 2016-05-13 5:37 Jason Zaman 2015-12-17 16:10 Jason Zaman 2015-10-26 5:36 [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2015-10-26 5:48 ` [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2015-03-29 9:59 Jason Zaman 2015-02-15 17:39 Sven Vermeulen 2014-12-04 1:46 Jason Zaman 2014-11-27 8:31 Jason Zaman 2014-09-21 14:08 [gentoo-commits] proj/hardened-refpolicy:mailinfra " Sven Vermeulen 2014-09-13 9:38 ` [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen 2014-06-25 19:06 Sven Vermeulen 2014-03-17 8:24 Sven Vermeulen 2014-03-17 8:24 Sven Vermeulen 2014-03-17 8:24 Sven Vermeulen 2014-03-06 15:20 Sven Vermeulen 2014-01-19 19:01 Sven Vermeulen 2013-09-30 19:03 Sven Vermeulen 2013-09-30 19:03 Sven Vermeulen 2013-09-26 13:19 Sven Vermeulen 2013-09-23 13:31 Sven Vermeulen 2013-09-23 6:29 [gentoo-commits] proj/hardened-refpolicy:merge " Sven Vermeulen 2013-09-23 13:31 ` [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen 2013-09-23 6:29 [gentoo-commits] proj/hardened-refpolicy:merge " Sven Vermeulen 2013-09-23 13:31 ` [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen 2013-05-01 18:23 Sven Vermeulen 2013-05-01 18:23 Sven Vermeulen 2013-01-16 19:48 Sven Vermeulen 2012-12-08 12:41 Sven Vermeulen 2012-12-03 21:03 Sven Vermeulen 2012-12-03 9:35 Sven Vermeulen 2012-11-06 20:21 Sven Vermeulen 2012-10-27 11:06 Sven Vermeulen 2012-10-22 18:15 Sven Vermeulen 2012-10-17 17:41 Sven Vermeulen 2012-10-16 17:39 Sven Vermeulen 2012-10-16 17:39 Sven Vermeulen 2012-10-16 17:39 Sven Vermeulen 2012-10-06 17:14 Sven Vermeulen 2012-10-06 17:05 Sven Vermeulen 2012-10-06 17:05 Sven Vermeulen 2012-10-06 15:56 Sven Vermeulen 2012-10-06 15:56 Sven Vermeulen 2012-10-04 17:36 Sven Vermeulen 2012-10-04 17:36 Sven Vermeulen 2012-10-04 17:36 Sven Vermeulen 2012-10-02 18:11 Sven Vermeulen 2012-10-02 18:11 Sven Vermeulen 2012-09-27 18:05 Sven Vermeulen 2012-09-27 18:05 Sven Vermeulen
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=1416673477.8417dc67710b700fb07902f2061e4e5856a6dfa6.swift@gentoo \ --to=swift@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: linkBe 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