| 1 |
Am Samstag, 2. November 2013, 16:03:30 schrieb Michał Górny: |
| 2 |
> Dnia 2013-11-02, o godz. 14:51:26 |
| 3 |
> |
| 4 |
> Tom Wijsman <TomWij@g.o> napisał(a): |
| 5 |
> > On Sat, 02 Nov 2013 09:16:45 -0400 |
| 6 |
> > |
| 7 |
> > "Anthony G. Basile" <blueness@g.o> wrote: |
| 8 |
> > > This is a followup to a discussion on IRC yesterday regarding |
| 9 |
> > > breakage that's occurring to catalyst builds as a result of the |
| 10 |
> > > recent move from dev-python/python-exec to dev-lang/python-exec. |
| 11 |
> > |
| 12 |
> > This has been happening to users as well, for example: |
| 13 |
> > |
| 14 |
> > http://forums.gentoo.org/viewtopic-t-973998.html |
| 15 |
> > http://forums.gentoo.org/viewtopic-t-974412.html |
| 16 |
> |
| 17 |
> From what I heard, most of people get this working through a plain: |
| 18 |
> |
| 19 |
> emerge -Du @world |
| 20 |
> |
| 21 |
> If someone is really reluctant to world updates, it is enough to |
| 22 |
> upgrade dev-python/python-exec to 10000.*: |
| 23 |
> |
| 24 |
> emerge -1v dev-python/python-exec |
| 25 |
|
| 26 |
I tried the world upgrade (yes, with --deep and with "--with-bdeps y" also) to |
| 27 |
no avail. |
| 28 |
|
| 29 |
"emerge -1av --nodeps $(qdepends -q -N -C -Q python-exec)" just wanted to |
| 30 |
rebuild app-portage/smart-live-rebuild - needless to say this didn't solve |
| 31 |
anything. |
| 32 |
|
| 33 |
Even unmerging python-exec didn't help. |
| 34 |
|
| 35 |
The blocker output was the following: |
| 36 |
|
| 37 |
===== |
| 38 |
Conflict: 1 block |
| 39 |
|
| 40 |
!!! Multiple package instances within a single package slot have been pulled |
| 41 |
!!! into the dependency graph, resulting in a slot conflict: |
| 42 |
|
| 43 |
dev-lang/python-exec:0 |
| 44 |
|
| 45 |
(dev-lang/python-exec-0.9999::gentoo, ebuild scheduled for merge) pulled in |
| 46 |
by |
| 47 |
dev-lang/python-exec:0[python_targets_jython2_5(-)?, |
| 48 |
python_targets_jython2_7(-)?, python_targets_pypy2_0(-)?, |
| 49 |
python_targets_python3_2(-)?, python_targets_python3_3(-)?, |
| 50 |
python_targets_python2_6(-)?, python_targets_python2_7(-)?, - |
| 51 |
python_single_target_jython2_5(-), -python_single_target_jython2_7(-), - |
| 52 |
python_single_target_pypy2_0(-), -python_single_target_python3_2(-), - |
| 53 |
python_single_target_python3_3(-), -python_single_target_python2_6(-), - |
| 54 |
python_single_target_python2_7(-)] required by (dev-python/python- |
| 55 |
exec-10000.1::gentoo, ebuild scheduled for merge) |
| 56 |
|
| 57 |
(dev-lang/python-exec-0.3.1::gentoo, ebuild scheduled for merge) pulled in |
| 58 |
by |
| 59 |
(no parents that aren't satisfied by other packages in this slot) |
| 60 |
|
| 61 |
|
| 62 |
!!! Enabling --newuse and --update might solve this conflict. |
| 63 |
!!! If not, it might help emerge to give a more specific suggestion. |
| 64 |
|
| 65 |
|
| 66 |
The following keyword changes are necessary to proceed: |
| 67 |
(see "package.accept_keywords" in the portage(5) man page for more details) |
| 68 |
# required by dev-python/PyQt4-4.10.2 |
| 69 |
# required by kde-misc/synaptiks-0.8.1-r4 |
| 70 |
# required by @kde_sed |
| 71 |
# required by @selected |
| 72 |
# required by @world (argument) |
| 73 |
=dev-lang/python-exec-0.9999 ** |
| 74 |
===== |
| 75 |
|
| 76 |
PyQt4 and synaptiks were only the messengers, btw. |
| 77 |
dev-lang/python-exec-0.9999 has the Targets pypy2_0 and python3_3 which dev- |
| 78 |
lang/python-exec-0.3.1 does not have. But both dev-python/python-exec-10000.1 |
| 79 |
and dev-python/python-exec-10000.2 want a dev-lang/python-exec:0 with the same |
| 80 |
target setting. |
| 81 |
|
| 82 |
Btw. Why does dev-python/python-exec:2 has a dependency on dev-python/python- |
| 83 |
exec:0 ? |
| 84 |
|
| 85 |
|
| 86 |
Cheers |
| 87 |
|
| 88 |
Sven |
Archives