public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jason Zaman" <perfinion@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-libs/libsepol/
Date: Mon, 21 Dec 2015 08:57:38 +0000 (UTC)	[thread overview]
Message-ID: <1450688196.969878ce4026fabbec440db7aaa4cc0dff505389.perfinion@gentoo> (raw)

commit:     969878ce4026fabbec440db7aaa4cc0dff505389
Author:     Jason Zaman <perfinion <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 21 02:49:38 2015 +0000
Commit:     Jason Zaman <perfinion <AT> gentoo <DOT> org>
CommitDate: Mon Dec 21 08:56:36 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=969878ce

sys-libs/libsepol: migrate selinux herd to project

Package-Manager: portage-2.2.24

 sys-libs/libsepol/metadata.xml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/sys-libs/libsepol/metadata.xml b/sys-libs/libsepol/metadata.xml
index a19075f..0c8cd5b 100644
--- a/sys-libs/libsepol/metadata.xml
+++ b/sys-libs/libsepol/metadata.xml
@@ -1,7 +1,10 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
-	<herd>selinux</herd>
+	<maintainer>
+		<email>selinux@gentoo.org</email>
+		<name>SELinux Team</name>
+	</maintainer>
 	<longdescription>SELinux library for manipulating binary security policies</longdescription>
 	<upstream>
 		<remote-id type="github">SELinuxProject/selinux</remote-id>


             reply	other threads:[~2015-12-21  8:57 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21  8:57 Jason Zaman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-13 19:47 [gentoo-commits] repo/gentoo:master commit in: sys-libs/libsepol/ Sven Vermeulen
2016-06-01 14:15 Jason Zaman
2016-08-07 17:07 Jason Zaman
2016-09-01 16:31 Jason Zaman
2016-10-03  7:30 Jason Zaman
2016-10-07  4:24 Jason Zaman
2016-10-24 15:39 Jason Zaman
2016-12-12 14:01 Jason Zaman
2017-06-13 15:20 Jason Zaman
2017-06-13 15:20 Jason Zaman
2017-07-09 10:03 Jason Zaman
2017-07-09 10:03 Jason Zaman
2017-07-22 11:08 Jason Zaman
2017-07-22 11:08 Jason Zaman
2017-08-07 16:48 Jason Zaman
2017-08-07 16:48 Jason Zaman
2017-09-23  2:15 Jason Zaman
2017-09-23  2:15 Jason Zaman
2018-04-26 11:22 Jason Zaman
2018-04-26 11:22 Jason Zaman
2018-04-27  4:45 Jason Zaman
2018-04-27  4:45 Jason Zaman
2018-05-13 17:28 Jason Zaman
2018-05-13 17:28 Jason Zaman
2018-05-25  7:29 Jason Zaman
2018-05-25  7:29 Jason Zaman
2018-06-26  2:07 Jason Zaman
2019-02-09 11:49 Jason Zaman
2019-02-09 11:49 Jason Zaman
2019-03-31 13:46 Jason Zaman
2019-03-31 13:46 Jason Zaman
2019-08-17 10:09 Jason Zaman
2019-08-17 10:09 Jason Zaman
2019-12-02 14:50 Jason Zaman
2019-12-08 17:26 Jason Zaman
2019-12-08 17:26 Jason Zaman
2019-12-08 18:39 Jason Zaman
2020-02-11 19:43 Agostino Sarubbo
2020-02-11 19:50 Agostino Sarubbo
2020-07-01 17:34 Mike Gilbert
2020-09-15  3:41 Jason Zaman
2020-12-03  3:12 Jason Zaman
2020-12-18  3:31 Jason Zaman
2021-04-03  4:19 Jason Zaman
2021-04-03  4:19 Jason Zaman
2021-07-04 22:19 Sam James
2021-07-28 20:08 Sam James
2021-10-31  2:55 Sam James
2021-11-20 23:20 Sam James
2021-11-20 23:20 Sam James
2021-12-28  1:14 Jason Zaman
2022-04-09  2:55 Jason Zaman
2022-04-11  3:44 Jason Zaman
2022-04-11  4:59 Jason Zaman
2022-06-04  1:03 Kenton Groombridge
2022-06-04  1:03 Kenton Groombridge
2022-07-02 17:03 Kenton Groombridge
2022-07-18 12:49 Sam James
2022-07-18 12:49 Sam James
2023-03-30  0:09 Kenton Groombridge
2023-03-30  0:09 Kenton Groombridge
2023-04-09 15:14 Kenton Groombridge
2023-04-15 15:13 Kenton Groombridge
2024-01-17  1:33 Kenton Groombridge
2024-01-17  1:33 Kenton Groombridge
2024-02-09 14:41 Kenton Groombridge
2024-06-30  0:36 Jason Zaman
2024-06-30  0:49 Jason Zaman
2024-07-19  9:57 James Le Cuirot
2024-07-19  9:57 James Le Cuirot
2024-07-19 19:23 James Le Cuirot
2024-08-12  1:23 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=1450688196.969878ce4026fabbec440db7aaa4cc0dff505389.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