public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sven Vermeulen" <swift@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/selinux-python/
Date: Sun, 18 Jun 2017 14:34:28 +0000 (UTC)	[thread overview]
Message-ID: <1497796176.b169bf26e1cde951a1b123d4a390a38694f18971.swift@gentoo> (raw)

commit:     b169bf26e1cde951a1b123d4a390a38694f18971
Author:     Sven Vermeulen <swift <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 18 14:26:49 2017 +0000
Commit:     Sven Vermeulen <swift <AT> gentoo <DOT> org>
CommitDate: Sun Jun 18 14:29:36 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b169bf26

sys-apps/selinux-python: Have dependency blocker on older policycoreutils versions

The selinux-python package can only be installed after policycoreutils has been
upgraded. To accomplish that, a PDEPEND was put in place in policycoreutils.
However, in some situations Portage does not want to use this ordering. This
is expected behavior, because PDEPEND does not necessarily mean that the
package manager has to install it afterwards - it is just a notion that the
order doesn't matter.

In this case, it does. So in order to ensure that the order is maintained,
we add in a blocker dependency on the older policycoreutils in selinux-python.

See also bug 622102

Package-Manager: Portage-2.3.5, Repoman-2.3.1

 sys-apps/selinux-python/selinux-python-2.7_rc1.ebuild | 1 +
 1 file changed, 1 insertion(+)

diff --git a/sys-apps/selinux-python/selinux-python-2.7_rc1.ebuild b/sys-apps/selinux-python/selinux-python-2.7_rc1.ebuild
index 8064324267b..3589860c4de 100644
--- a/sys-apps/selinux-python/selinux-python-2.7_rc1.ebuild
+++ b/sys-apps/selinux-python/selinux-python-2.7_rc1.ebuild
@@ -39,6 +39,7 @@ DEPEND=">=sys-libs/libselinux-${SELNX_VER}:=[python]
 	>=app-admin/setools-4.0
 	dev-python/ipy[${PYTHON_USEDEP}]
 	!dev-python/sepolgen
+	!<sys-apps/policycoreutils-2.7_rc1
 	${PYTHON_DEPS}"
 
 RDEPEND="${DEPEND}"


             reply	other threads:[~2017-06-18 14:34 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-18 14:34 Sven Vermeulen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-06 12:37 [gentoo-commits] repo/gentoo:master commit in: sys-apps/selinux-python/ Sam James
2025-05-06 12:37 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-14 13:33 Arthur Zamarin
2025-02-14 13:31 Arthur Zamarin
2025-02-14 13:31 Arthur Zamarin
2025-02-09 22:45 Jason Zaman
2025-02-09 22:45 Jason Zaman
2025-02-08 22:19 Jason Zaman
2024-09-06 16:31 Arthur Zamarin
2024-08-12  1:23 Jason Zaman
2024-07-19 19:50 Jakov Smolić
2024-07-19 19:23 James Le Cuirot
2024-07-08 14:22 Kenton Groombridge
2024-06-30  0:49 Jason Zaman
2024-06-30  0:36 Jason Zaman
2024-06-06 13:49 Kenton Groombridge
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-09-07  7:52 Michał Górny
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-06-04  1:03 Kenton Groombridge
2022-04-11  4:59 Jason Zaman
2022-04-11  3:44 Jason Zaman
2021-12-28  1:14 Jason Zaman
2021-11-20 23:21 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-19 22:22 Sam James
2021-07-19 22:21 Sam James
2021-07-19 22:21 Sam James
2021-07-04 22:19 Sam James
2021-04-03  4:19 Jason Zaman
2021-04-03  4:19 Jason Zaman
2021-02-07  4:19 Jason Zaman
2021-02-07  4:19 Jason Zaman
2021-01-03  8:20 Jason Zaman
2020-12-18  3:31 Jason Zaman
2020-12-03  3:12 Jason Zaman
2020-10-25 21:29 Jason Zaman
2020-09-15  3:41 Jason Zaman
2020-07-02 13:22 Ben Kohler
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-12-27 11:26 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-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
2018-03-02  6:27 Jason Zaman
2017-09-23  2:15 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
2017-04-20 16:41 David Seifert
2017-02-23 11:22 Jason Zaman
2016-11-20  5:27 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=1497796176.b169bf26e1cde951a1b123d4a390a38694f18971.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: 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