| 1 |
Is it perhaps an idea to mask the gentoolkit package when updating portage? |
| 2 |
|
| 3 |
|
| 4 |
On 12-08-16 14:42, Neil Bothwick wrote: |
| 5 |
> On Fri, 12 Aug 2016 14:16:25 +0200, hw wrote: |
| 6 |
> |
| 7 |
>> sys-apps/portage:0 |
| 8 |
>> |
| 9 |
>> (sys-apps/portage-2.2.28:0/0::gentoo, ebuild scheduled for merge) |
| 10 |
>> pulled in by sys-apps/portage (Argument) |
| 11 |
>> |
| 12 |
>> (sys-apps/portage-2.2.14:0/0::gentoo, installed) pulled in by |
| 13 |
>> 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(-)] |
| 14 |
>> required by (app-portage/gentoolkit-0.3.0.9-r2:0/0::gentoo, installed) |
| 15 |
>> |
| 16 |
>> |
| 17 |
>> So portage cannot be installed because portage is installed? |
| 18 |
> Rather it looks like portage can't be updated because of the version of |
| 19 |
> gentoolkit that is installed. Try uninstalling gentoolkit, updating |
| 20 |
> portage and then reinstalling gentoolkit. |
| 21 |
> |
| 22 |
> It may also help to know the USE flags used for gentoolkit and the |
| 23 |
> *current* portage install. |
| 24 |
> |
| 25 |
> |
Archives