On 03/30/2018 08:01 AM, Kai Krakow wrote:
> Am Tue, 13 Mar 2018 14:52:34 -0600 schrieb thelma:
>
>> Thelma
>> On 03/13/2018 12:11 PM, Neil Bothwick wrote:
>>> On Tue, 13 Mar 2018 11:36:12 -0600, the...@sys-concept.com wrote:
>>>
>>>> sys-apps/portage:0
>>>>
>>>> (sys-apps/portage-2.3.16:0/0::gentoo, ebuild scheduled for merge)
>>>> pulled in by sys-apps/portage (Argument)
>>>>
>>>> (sys-apps/portage-2.3.6:0/0::gentoo, installed) pulled in by
>>>>
>>>> sys-apps/portage[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)]
>>>> required by (app-portage/gentoolkit-0.3.3:0/0::gentoo, installed)
>>>
>>> Your old version of gentoolkit (and other packages mentioned in the full
>>> output) is causing this. Trying to upgrade an out of date system
>>> piecemeal can cause this. Just do an emerge -u @system and let portage
>>> resolve these issues rather than trying to do it yourself.
>>
>> I spoke too soon. Now, when I try: emerge -u @system
>> I'm getting an error as well.
>>
>> emerge -ua @system
>>
>> These are the packages that would be merged, in order:
>>
>> Calculating dependencies... done!
>>
>> WARNING: One or more updates/rebuilds have been skipped due to a dependency
>> conflict:
>>
>> sys-libs/zlib:0
>>
>> (sys-libs/zlib-1.2.11-r1:0/1::gentoo, ebuild scheduled for merge)
>> conflicts with
>> >=sys-libs/zlib-1.2.8-r1:0/0=[abi_x86_32(-),abi_x86_64(-)] required by
>> (media-libs/lcms-2.8-r1:2/2::gentoo, installed)
>> ^^^^^
> |
> Note this ----------------------+
>
>>
>> sys-libs/readline:0
>>
>> (sys-libs/readline-7.0_p3:0/7::gentoo, ebuild scheduled for merge)
>> conflicts with
>> sys-libs/readline:0/0= required by (dev-lang/ruby-2.1.9:2.1/2.1::gentoo,
>> installed)
>> ^^^^^
> |
> And this too ------------+
>
>> !!! The following update(s) have been skipped due to unsatisfied dependencies
>> !!! triggered by backtracking:
>>
>> app-shells/bash:0
>
> Emerge seems to be unable to resolve subslot changes properly and
> doesn't issue a rebuild automatically for those. It's a headache I
> regularly have to deal with when upgrading Qt.
>
> As you can see from the output, the subslot requirement changed from
> "0/0" (as required by lcms) to "0/1" (as required by your emerge
> request). Similar goes for readline and ruby.
>
> As written in the other post, you can usually inject those reinstalls
> manually with:
>
> # emerge ... --reinstall-atoms={lcms,ruby}
>
> If you are using color output, these are usually easily spotted as
> they are the blue package names.
THANK YOU! for the explanation.
Finally somebody was able to explain it clearly.
I've added your explanation to my special notes. Next time I'll know
what to do.
Happy Easter!
--
Thelma
