| 1 |
PS: Sorry, I tried it in a container. Here´s what I get on the host: |
| 2 |
|
| 3 |
|
| 4 |
emerge -1a portage |
| 5 |
[...] |
| 6 |
[ebuild N ] sys-apps/install-xattr-0.5 |
| 7 |
[ebuild N ] dev-python/packaging-15.3-r2 USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 (-pypy) (-pypy3) -python3_3 (-python3_5)" |
| 8 |
[ebuild U ] dev-python/setuptools-18.4 [7.0] PYTHON_TARGETS="python3_4* -python3_3* (-python3_5)" |
| 9 |
[ebuild N ] dev-python/certifi-2015.11.20 PYTHON_TARGETS="python2_7 python3_4 (-pypy) (-pypy3) -python3_3 (-python3_5)" |
| 10 |
[ebuild N ] dev-python/pyxattr-0.5.5 USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_4 (-pypy) -python3_3 (-python3_5)" |
| 11 |
[ebuild U ] sys-apps/portage-2.2.28 [2.2.14] USE="xattr*" PYTHON_TARGETS="python3_4* -python3_3* (-python3_5)" |
| 12 |
|
| 13 |
!!! Multiple package instances within a single package slot have been pulled |
| 14 |
!!! into the dependency graph, resulting in a slot conflict: |
| 15 |
|
| 16 |
dev-python/setuptools:0 |
| 17 |
|
| 18 |
(dev-python/setuptools-18.4:0/0::gentoo, ebuild scheduled for merge) pulled in by |
| 19 |
dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] required by (dev-python/certifi-2015.11.20:0/0::gentoo, ebuild scheduled for merge) |
| 20 |
|
| 21 |
dev-python/setuptools[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] required by (dev-python/pyxattr-0.5.5:0/0::gentoo, ebuild scheduled for merge) |
| 22 |
|
| 23 |
|
| 24 |
(dev-python/setuptools-7.0:0/0::gentoo, installed) pulled in by |
| 25 |
dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_pypy(-)] required by (dev-python/cryptography-0.6.1:0/0::gentoo, installed) |
| 26 |
|
| 27 |
dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-)] required by (dev-python/chardet-2.2.1:0/0::gentoo, installed) |
| 28 |
|
| 29 |
|
| 30 |
sys-apps/portage:0 |
| 31 |
|
| 32 |
(sys-apps/portage-2.2.28:0/0::gentoo, ebuild scheduled for merge) pulled in by |
| 33 |
sys-apps/portage (Argument) |
| 34 |
|
| 35 |
(sys-apps/portage-2.2.14:0/0::gentoo, installed) pulled in by |
| 36 |
sys-apps/portage[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-)] required by (app-portage/gentoolkit-0.3.0.9-r2:0/0::gentoo, installed) |
| 37 |
|
| 38 |
sys-apps/portage[python_targets_python2_7(-)?,python_targets_python3_3(-)?,-python_single_target_python2_7(-),-python_single_target_python3_3(-)] required by (app-admin/webapp-config-1.52-r1:0/0::gentoo, installed) |
| 39 |
|
| 40 |
|
| 41 |
Neil Bothwick schrieb: |
| 42 |
> On Wed, 10 Aug 2016 12:54:37 +0200, hw wrote: |
| 43 |
> |
| 44 |
>> emerge -a portage --newuse --update |
| 45 |
> |
| 46 |
> That tries to updates deps too, try this |
| 47 |
> |
| 48 |
> emerge -1a portage |
| 49 |
> |
| 50 |
> or even, if that still fails |
| 51 |
> |
| 52 |
> emerge -1a --nodeps portage |
| 53 |
> |
| 54 |
> |
| 55 |
|
| 56 |
emerge -1a portage |
| 57 |
[...] |
| 58 |
Calculating dependencies... done! |
| 59 |
[ebuild N ] sys-apps/install-xattr-0.5 |
| 60 |
[ebuild N ] dev-python/packaging-15.3-r2 USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 (-pypy) (-pypy3) -python3_3 (-python3_5)" |
| 61 |
[ebuild N ] dev-python/setuptools-18.4 USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 (-pypy) (-pypy3) -python3_3 (-python3_5)" |
| 62 |
[ebuild N ] dev-python/certifi-2015.11.20 PYTHON_TARGETS="python2_7 python3_4 (-pypy) (-pypy3) -python3_3 (-python3_5)" |
| 63 |
[ebuild N ] dev-python/pyxattr-0.5.5 USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_4 (-pypy) -python3_3 (-python3_5)" |
| 64 |
[ebuild U ] sys-apps/portage-2.2.28 [2.2.14] USE="xattr*" PYTHON_TARGETS="python3_4* -python3_3* (-python3_5)" |
| 65 |
|
| 66 |
!!! Multiple package instances within a single package slot have been pulled |
| 67 |
!!! into the dependency graph, resulting in a slot conflict: |
| 68 |
|
| 69 |
sys-apps/portage:0 |
| 70 |
|
| 71 |
(sys-apps/portage-2.2.28:0/0::gentoo, ebuild scheduled for merge) pulled in by |
| 72 |
sys-apps/portage (Argument) |
| 73 |
|
| 74 |
(sys-apps/portage-2.2.14:0/0::gentoo, installed) pulled in by |
| 75 |
sys-apps/portage[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-)] required by (app-portage/gentoolkit-0.3.0.9-r2:0/0::gentoo, installed) |
| 76 |
|
| 77 |
|
| 78 |
So portage cannot be installed because portage is installed? |
| 79 |
|
| 80 |
When I use --nodeps, portage might not work at all anymore and I would be |
| 81 |
totally screwed. And 'emerge -1a --newuse --update portage' gives the |
| 82 |
same result. |
Archives