Am Samstag, 2. November 2013, 16:03:30 schrieb Michał Górny: > Dnia 2013-11-02, o godz. 14:51:26 > > Tom Wijsman <tom...@gentoo.org> napisał(a): > > On Sat, 02 Nov 2013 09:16:45 -0400 > > > > "Anthony G. Basile" <bluen...@gentoo.org> wrote: > > > This is a followup to a discussion on IRC yesterday regarding > > > breakage that's occurring to catalyst builds as a result of the > > > recent move from dev-python/python-exec to dev-lang/python-exec. > > > > This has been happening to users as well, for example: > > > > http://forums.gentoo.org/viewtopic-t-973998.html > > http://forums.gentoo.org/viewtopic-t-974412.html > > From what I heard, most of people get this working through a plain: > > emerge -Du @world > > If someone is really reluctant to world updates, it is enough to > upgrade dev-python/python-exec to 10000.*: > > emerge -1v dev-python/python-exec
I tried the world upgrade (yes, with --deep and with "--with-bdeps y" also) to
no avail.
"emerge -1av --nodeps $(qdepends -q -N -C -Q python-exec)" just wanted to
rebuild app-portage/smart-live-rebuild - needless to say this didn't solve
anything.
Even unmerging python-exec didn't help.
The blocker output was the following:
=====
Conflict: 1 block
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-lang/python-exec:0
(dev-lang/python-exec-0.9999::gentoo, ebuild scheduled for merge) pulled in
by
dev-lang/python-exec:0[python_targets_jython2_5(-)?,
python_targets_jython2_7(-)?, python_targets_pypy2_0(-)?,
python_targets_python3_2(-)?, python_targets_python3_3(-)?,
python_targets_python2_6(-)?, python_targets_python2_7(-)?, -
python_single_target_jython2_5(-), -python_single_target_jython2_7(-), -
python_single_target_pypy2_0(-), -python_single_target_python3_2(-), -
python_single_target_python3_3(-), -python_single_target_python2_6(-), -
python_single_target_python2_7(-)] required by (dev-python/python-
exec-10000.1::gentoo, ebuild scheduled for merge)
(dev-lang/python-exec-0.3.1::gentoo, ebuild scheduled for merge) pulled in
by
(no parents that aren't satisfied by other packages in this slot)
!!! Enabling --newuse and --update might solve this conflict.
!!! If not, it might help emerge to give a more specific suggestion.
The following keyword changes are necessary to proceed:
(see "package.accept_keywords" in the portage(5) man page for more details)
# required by dev-python/PyQt4-4.10.2
# required by kde-misc/synaptiks-0.8.1-r4
# required by @kde_sed
# required by @selected
# required by @world (argument)
=dev-lang/python-exec-0.9999 **
=====
PyQt4 and synaptiks were only the messengers, btw.
dev-lang/python-exec-0.9999 has the Targets pypy2_0 and python3_3 which dev-
lang/python-exec-0.3.1 does not have. But both dev-python/python-exec-10000.1
and dev-python/python-exec-10000.2 want a dev-lang/python-exec:0 with the same
target setting.
Btw. Why does dev-python/python-exec:2 has a dependency on dev-python/python-
exec:0 ?
Cheers
Sven
signature.asc
Description: This is a digitally signed message part.
