public inbox for
 help / color / mirror / Atom feed
From: "Martin Liška" <>
To: Jonathan Wakely <>,
	"Frank Ch. Eigler" <>
Cc: Overseers mailing list <>,
	gcc-patches <>,
	"Frank Ch. Eigler" <>
Subject: Re: [PATCH] contrib: use sphinx-build from a venv
Date: Tue, 26 Jul 2022 14:17:19 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 7/26/22 14:01, Jonathan Wakely via Gcc-patches wrote:
> On Tue, 26 Jul 2022 at 12:56, Frank Ch. Eigler wrote:
>> Hi -
>>>> The gccadmin team can do this kind of thing without overseer/root
>>>> privileges, or indeed so can any local shell-privileged user.
>>> Yeah, I said I didn't want to install it that way without overseer
>>> approval, as pip won't keep the packages up to date the way dnf
>>> installations do.
>> Indeed, but that's your own preference/responsibility and does not
>> affect the system, so no overseer oversight is necessary.
> OK, I can install it for Martin then.

Thanks Jonathan.

>>>> (That said, rhel8 includes sphynx 1.7.6 - are you sure that's
>>>> not satisfactory?)
>>> That's a different package (full text search engine), what's needed
>>> here is python3-sphinx.
>> # rpm -q python3-sphinx
>> python3-sphinx-1.7.6-2.el8.noarch
> Oh right, yes, sorry, I got confused after I looked into the packages
> myself. The "other sphinx" is in EPEL 8 as sphinx-2.2.11-15.el8

Sorry, but it's too old, we actually need a release that was released this week ;)


      reply	other threads:[~2022-07-26 12:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2022-07-26  7:26 ` Martin Liška
2022-07-26 11:45   ` Frank Ch. Eigler
2022-07-26 11:54     ` Jonathan Wakely
2022-07-26 11:56       ` Frank Ch. Eigler
2022-07-26 12:01         ` Jonathan Wakely
2022-07-26 12:17           ` Martin Liška [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).