Bug 522974 – sys-apps/portage: Broken dependencies on selinux for multiple depending packages

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Patrick Lauer 2014-09-17 02:22:51 UTC]

app-admin/webapp-config-1.53.ebuild: ['sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_pypy(-)]']
app-portage/diffmask-0.3.3-r2.ebuild: ['sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_pypy(-)]']
app-portage/gentoolkit-0.3.0.9-r1.ebuild: ['sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_pypy(-)]']
app-portage/layman-2.1.0-r3.ebuild: ['sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_pypy(-)]']

specifically:

  dependency.bad                6
   app-portage/gentoolkit/gentoolkit-0.3.0.9-r1.ebuild: DEPEND: ~amd64(hardened/linux/amd64/no-multilib/selinux) ['sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_pypy(-)]']
   app-portage/gentoolkit/gentoolkit-0.3.0.9-r1.ebuild: RDEPEND: ~amd64(hardened/linux/amd64/no-multilib/selinux) ['sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_pypy(-)]']
   app-portage/gentoolkit/gentoolkit-0.3.0.9-r1.ebuild: DEPEND: ~amd64(hardened/linux/amd64/selinux) ['sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_pypy(-)]']
   app-portage/gentoolkit/gentoolkit-0.3.0.9-r1.ebuild: RDEPEND: ~amd64(hardened/linux/amd64/selinux) ['sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_pypy(-)]']
   app-portage/gentoolkit/gentoolkit-0.3.0.9-r1.ebuild: DEPEND: ~x86(hardened/linux/x86/selinux) ['sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_pypy(-)]']
   app-portage/gentoolkit/gentoolkit-0.3.0.9-r1.ebuild: RDEPEND: ~x86(hardened/linux/x86/selinux) ['sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_pypy(-)]']

[Comment 1 Patrick Lauer 2014-09-17 02:26:47 UTC]

Looks like PYTHON_TARGETS is incomplete for pypy:

gentoolkit: PYTHON_COMPAT=(python{2_6,2_7,3_2,3_3} pypy pypy2_0)
portage: PYTHON_COMPAT=(pypy python3_2 python3_3 python3_4 python2_7)

==> pypy2_0 is absent in portage ? (Although older versions have that, and not pypy ... I guess the pypy keywords need to be synchronized between all versions)

[Comment 2 Brian Dolbec (RETIRED) 2014-09-17 04:06:04 UTC]

yeah, pypy2_* are obsolete.  On the new portage-2.2.13 I just released, it drops the old pypy2_* target.  

So, do I need to add it back in for now? Or do we remove pypy2_* from gentoolkit, layman?

Layman will have another release probably next weekend.

Also, the old portage ebuilds had a bug in them, so the libselinux and pypy deps did not spit out dep.bad warnings from repoman.  I discovered it with this new EAPI 5/setup.py ebuild.

[Comment 3 Michał Górny 2014-09-17 06:59:59 UTC]

No, it's not about pypy2_0. It is disabled and the eclass ignores it.

[Comment 4 Michał Górny 2014-09-17 07:18:17 UTC]

Oh, I know what it is :). We've disabled pypy support in Portage for selinux profiles since it doesn't work with emerge. However, we may want to reconsider this for the general utility modules...

[Comment 5 Brian Dolbec (RETIRED) 2014-09-17 16:16:40 UTC]

They all dep on portage so all get the same repoman dep.bad.

I've fixed it to mask pypyp for all the affected pkgs.  This has stopped the errors.