From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] docutils needing py2.7, but not wanting py2.7?
Date: Fri, 5 Jun 2020 03:43:33 -0500 [thread overview]
Message-ID: <53e1341e-57c4-0313-d8c0-50bdc5b3cdab@gmail.com> (raw)
In-Reply-To: <20200605090917.1332992a@digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
Neil Bothwick wrote:
> On Thu, 4 Jun 2020 23:42:50 +0100, Ashley Dixon wrote:
>
>> 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.
> Except that etc-update also adds a backtrace as comments, allowing him to
> trace the cause.
>
>
That backtrace is in the OP's original post. The first one doesn't give
much of one, none really. The second one gives a list of packages.
Either way, it was a circular problem. It seems the emerge --info for
the package gave the clue which I don't see anywhere in the output of
emerge.
Dale
:-) :-)
[-- Attachment #2: Type: text/html, Size: 1219 bytes --]
prev parent reply other threads:[~2020-06-05 8:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 21:24 [gentoo-user] docutils needing py2.7, but not wanting py2.7? Caveman Al Toraboran
2020-06-04 21:43 ` Ashley Dixon
2020-06-04 23:38 ` Caveman Al Toraboran
2020-06-05 0:20 ` Ashley Dixon
2020-06-05 0:54 ` Caveman Al Toraboran
2020-06-05 1:08 ` Ashley Dixon
2020-06-05 1:17 ` Caveman Al Toraboran
2020-06-04 21:47 ` Dale
2020-06-04 22:14 ` Neil Bothwick
2020-06-04 22:31 ` Dale
2020-06-04 22:42 ` Ashley Dixon
2020-06-04 22:56 ` Dale
2020-06-04 23:06 ` Ashley Dixon
2020-06-04 23:39 ` Sean O'Myers
2020-06-04 23:49 ` [OT] " Ashley Dixon
2020-06-05 8:09 ` Neil Bothwick
2020-06-05 8:43 ` Dale [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53e1341e-57c4-0313-d8c0-50bdc5b3cdab@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox