Re: [gentoo-user] docutils needing py2.7, but not wanting py2.7?

[Dale <rdalek1967@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2085 bytes --]

Ashley Dixon wrote:
> On Thu, Jun 04, 2020 at 05:31:29PM -0500, Dale wrote:
>> Neil Bothwick wrote:
>>> Allow portage to add the changes to your config, then run etc-update or
>>> equivalent. When portage adds package.use changes, it also adds comments
>>> showing what requires those changes. With that information, you should be
>>> able to see which package is causing this.
>> One of us is reading that wrong.  Given my eyes, maybe it is me.  My new
>> glasses should be in within the next week or so.  In the first instance,
>> it wants py2.7 disabled.  So he adds it to the config file to disable
>> it.  When he runs the command again, it wants to enable py2.7 for the
>> same package and version.  If I'm reading that right, even if he lets
>> emerge add the change, it will lead to two problems.  One, there will be
>> one line enabling py2.7 and another line disabling it.  If I recall
>> correctly, emerge will take the last one.  Two, he will be back to the
>> first problem, it wanting py2.7 disabled.  In other words, back where he
>> started. 
>>
>> Am I reading that wrong or something?? 
> Providing he's just adding the line to a package.use file with  a  text  editor,
> that's just manually doing the work of etc-update.  We need the  `emerge  --info
> docutils` output to see full information about his Python environment.
>

True but it asks for one thing, then when it is done, it asks for it to
be undone.  I agree something is off somewhere but I'm not sure using
etc-update is going to matter.  I do my edits manually as well and
rarely use etc-update and friends.  Whether done manually or with the
tool, the result is the same.  The comments it will add to those files
are listed in the outputs above.  I don't think that is going to shed
any new light on the problem either.

Seeing the output of emerge --info for that package may shed some light
on the problem but allowing etc-update to change the config isn't going
to help.  It's in one of its circular problems that comes from something
else. 

Maybe we will get more info shortly. 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 2705 bytes --]