Re: [gentoo-user] update fails, but I don't see why

[n952162]

On 12/13/20 10:55 AM, Michael wrote:
> On Sunday, 13 December 2020 08:57:53 GMT n952162 wrote:
>> On 12/13/20 9:18 AM, Neil Bothwick wrote:
>>> There's a lot to trawl through here, it looks like you haven't updated
>>>
>>>>> for quite some time.
>>>> The (compressed) log of  a system and world update from 20. October
>>>> (2020!) is attached.
>>> Nearly 2 months, quite a long time in Gentoo update terms.
>> !!!  After 2 months the system can no longer be update-able?
> A system can be updated and updatable after more than two months, but be
> prepared for some manual intervention and a staged approach to running emerge.


(I just discoved your posting, thank you)

By staged approach, you mean first @system and then @world?  I've just
realized that doing this doesn't bring anything ;-)

     emerge ... @system @world


> Starting with 'eselect news read new' is advisable for any heads up to changes
> in gentoo, major packages and configuration.


Yeah, except I wouldn't know what to do about it.


>
> Also pay attention to any messages on the CLI when you run emerge about
> packages which are due to be removed from portage, as you will need to take
> care of these manually in your local or some external 3rd party overlay.


You mean, like get them out of my world file?


>
>
>>> ...
>>>
>>>>>     What do
>>>>>
>>>>> grep -r python3_6 /etc/portage
>>>> That showed that the only references are in package.use
>>> But what does it show. We need the output of commands, not some vague
>>> reference to them. I suspected there was something in package.use, but we
>>> need to know what. Those references should probably be removed but no one
>>> can say for sure without seeing them.
>> Oh sorry.  You mentioned
>>
>> PYTHON_TARGETS="python3_6"
>>
>> and I didn't connect that with USE variables.  Here there are (with comments
>> removed)
> It isn't just USE flags for python-3.6 you may have set up yourself, but USE
> flags for any python version you have specified.  Under normal circumstances
> you would not need to specify these yourself and pegging python at a
> particular version is bound to cause warnings later on, when that python
> version has been deprecated and is no longer available in portage.
>
>
>> $ sed -n -e '/^\s*#/d' -e '/python3_6/p' /etc/portage/package.use/*
>>
>>> =dev-python/certifi-10001-r1 python_targets_python3_6
>>> =dev-python/setuptools_scm-4.1.2-r1 python_targets_python3_6
>>> =dev-python/requests-2.24.0-r1 python_targets_python3_6
>>> =dev-python/chardet-3.0.4-r1 python_targets_python3_6
>>> =dev-python/idna-2.10-r1 python_targets_python3_6
>>> =dev-python/urllib3-1.25.11 python_targets_python3_6
>>> =dev-python/cryptography-3.2.1 python_targets_python3_6
>>> =dev-python/cffi-1.14.0-r3 python_targets_python3_6
>>> =dev-python/pycparser-2.20-r1 python_targets_python3_6
>>> =dev-python/ply-3.11-r1 python_targets_python3_6
>>> =dev-python/PySocks-1.7.1-r1 python_targets_python3_6
>>> =dev-python/pyopenssl-19.1.0-r1 python_targets_python3_6
>>> =dev-python/setuptools-50.3.0 python_targets_python3_6
>>> =dev-python/six-1.15.0-r1 python_targets_python3_6
> Why had you set up these in your package.use?


Basically, whenever emerge tells me I need USE variables, I define them.

It's not clear to me how I should know to override that, for example, to
say, oh that's not needed anymore.


>
> If you comment them out and re-run emerge are you getting any more warnings/
> errors?


Yes, those are all gone.