From: "Martin Liška" <mliska@suse.cz>
To: "Frank Ch. Eigler" <fche@redhat.com>,
Overseers mailing list <overseers@sourceware.org>
Cc: Mark Wielaard <mark@klomp.org>, "Frank Ch. Eigler" <fche@elastic.org>
Subject: Re: Server package installation - Sphinx
Date: Tue, 8 Nov 2022 12:19:00 +0100 [thread overview]
Message-ID: <b8330a6f-3543-b4d3-e2fe-c380996e3d1d@suse.cz> (raw)
In-Reply-To: <20221108090037.GD20095@redhat.com>
On 11/8/22 10:00, Frank Ch. Eigler wrote:
> Hi -
>
>> For now, I would need to update the existing env:
>> $ /home/gccadmin/venv/bin/pip --upgrade sphinx
>> and add Sphinx deps:
>> $ /home/gccadmin/venv/bin/pip install furo sphinx-copybutton
>
> The gccadmin shared userid should be able to do all these things,
> please reach out to those folks.
>
>> Apart from that, I will need Texlive-related packages:
>> python-sphinx-latex
>> texlive-xindy
>
> The former's installed. The latter does not appear available
> on rhel8+epel8.
Hello.
Thanks, xindy won't be needed and Mark helped me with updating the venv.
The PDF output seems fine.
Cheers,
Martin
>
> - FChE
>
prev parent reply other threads:[~2022-11-08 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 8:03 Martin Liška
2022-11-08 9:00 ` Frank Ch. Eigler
2022-11-08 11:19 ` 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:
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=b8330a6f-3543-b4d3-e2fe-c380996e3d1d@suse.cz \
--to=mliska@suse.cz \
--cc=fche@elastic.org \
--cc=fche@redhat.com \
--cc=mark@klomp.org \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).