public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sven Vermeulen" <sven.vermeulen@siphos.be>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-dev:master commit in: sys-apps/policycoreutils/
Date: Tue,  1 May 2012 13:47:57 +0000 (UTC)	[thread overview]
Message-ID: <1335880048.45e6b01b956a8fd884d73b46381257b1a1d2912f.SwifT@gentoo> (raw)

commit:     45e6b01b956a8fd884d73b46381257b1a1d2912f
Author:     Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
AuthorDate: Tue May  1 13:47:28 2012 +0000
Commit:     Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
CommitDate: Tue May  1 13:47:28 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-dev.git;a=commit;h=45e6b01b

Update manifest, wrong patch

---
 .../policycoreutils-2.1.10-r3.ebuild               |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/sys-apps/policycoreutils/policycoreutils-2.1.10-r3.ebuild b/sys-apps/policycoreutils/policycoreutils-2.1.10-r3.ebuild
index ee7ca71..3dd1c4a 100644
--- a/sys-apps/policycoreutils/policycoreutils-2.1.10-r3.ebuild
+++ b/sys-apps/policycoreutils/policycoreutils-2.1.10-r3.ebuild
@@ -26,6 +26,7 @@ SRC_URI="http://userspace.selinuxproject.org/releases/20120216/${P}.tar.gz
 	http://dev.gentoo.org/~swift/patches/policycoreutils/policycoreutils-2.1.10-fix-nodbus_or_libcg.patch.gz
 	http://dev.gentoo.org/~swift/patches/policycoreutils/policycoreutils-2.1.10-fix-rlpkg-python3.patch.gz
 	http://dev.gentoo.org/~swift/patches/policycoreutils/policycoreutils-2.1.10-seobject-python3.patch.gz
+	http://dev.gentoo.org/~swift/patches/policycoreutils/policycoreutils-2.1.10-semanage-python3.patch.gz
 	mirror://gentoo/policycoreutils-2.0.85-python3.tar.gz
 	mirror://gentoo/policycoreutils-extra-${EXTRAS_VER}.tar.bz2"
 
@@ -89,6 +90,7 @@ src_prepare() {
 	cp "${WORKDIR}/audit2allow" "${S}/audit2allow/audit2allow" || die "failed to copy audit2allow"
 	# Further patching for python3 support
 	epatch "${DISTDIR}/policycoreutils-2.1.10-seobject-python3.patch.gz"
+	epatch "${DISTDIR}/policycoreutils-2.1.10-semanage-python3.patch.gz"
 	# Fix rlpkg for python3 support
 	cd "${S2}";
 	epatch "${DISTDIR}/policycoreutils-2.1.10-fix-rlpkg-python3.patch.gz"



             reply	other threads:[~2012-05-01 13:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01 13:47 Sven Vermeulen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-06-16 18:03 [gentoo-commits] proj/hardened-dev:master commit in: sys-apps/policycoreutils/ Sven Vermeulen
2013-06-16 18:03 Sven Vermeulen
2013-03-08 19:20 Sven Vermeulen
2012-10-06 19:24 Sven Vermeulen
2012-10-03 19:42 Sven Vermeulen
2012-09-08 19:57 Sven Vermeulen
2012-08-14 18:54 Sven Vermeulen
2012-05-01 13:49 Sven Vermeulen
2012-05-01 13:39 Sven Vermeulen
2012-04-30 19:48 Sven Vermeulen
2011-12-30 19:54 Sven Vermeulen
2011-09-17 16:11 Sven Vermeulen
2011-09-13 18:57 Sven Vermeulen
2011-09-12 20:06 Sven Vermeulen
2011-07-08 15:49 Sven Vermeulen
2011-06-30 10:37 Anthony G. Basile
2011-06-29 12:50 Sven Vermeulen
2011-06-16  1:42 Anthony G. Basile
2011-06-15 18:19 Sven Vermeulen
2011-06-15 18:18 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=1335880048.45e6b01b956a8fd884d73b46381257b1a1d2912f.SwifT@gentoo \
    --to=sven.vermeulen@siphos.be \
    --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