linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: Akira Yokosawa <akiyks@gmail.com>,
	corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: freeze some package versions for sphinx virtualenv setup
Date: Tue, 27 Feb 2024 14:17:13 +0100	[thread overview]
Message-ID: <CAKXUXMzh4hznQNL+K_PrtJ-Ug1p0Q-JGOsTmAt=6fi4d07YOFw@mail.gmail.com> (raw)
In-Reply-To: <e5bf0fd4-9eab-48ee-b56a-7137c528d9ff@oracle.com>

On Tue, Feb 27, 2024 at 9:41 AM Vegard Nossum <vegard.nossum@oracle.com> wrote:
>
>
> On 27/02/2024 09:24, Lukas Bulwahn wrote:
> > On Tue, Feb 27, 2024 at 7:57 AM Akira Yokosawa <akiyks@gmail.com> wrote:
> >> On Mon, 26 Feb 2024 10:38:54 +0100, Lukas Bulwahn wrote:
> >>> Akira-san Yokosawa reported this already in January 2023 and Jani Nikula
> >>> was fast in providing a fix (see Link). This however remained as a thread
> >>> on the linux-doc mailing and was never turned into a patch for Jonathan to
> >>> pick up.
> >>
> >> Have you read Jon's message in the thread archived at:
> >>
> >>      https://lore.kernel.org/linux-doc/874jf4m384.fsf@meer.lwn.net/
> >>
> >> I think you can see why there had been no submission of a proper patch
> >> in your patch's direction nor others.
> >>
> >> If you still want your patch applied soon, you need to convince Jon.
>
> [...]
>
> > Hence, I proposed this patch here. It works (for me). But I do not
> > care if it is picked or not---because I am just continuing the
> > whack-a-mole game. As of now, I do not know how much work the better
> > solution for "updating to recent versions" needs. I will spend half a
> > day and hopefully I can then present a good working patch. But let us
> > see.
>
> I now locally have a file requirements-2.4.4.txt that was the result of
> running 'pip freeze' in a working Sphinx-2.4.4 virtualenv:
>
> alabaster==0.7.13
> Babel==2.14.0
> certifi==2024.2.2
> charset-normalizer==3.3.2
> docutils==0.20.1
> idna==3.6
> imagesize==1.4.1
> Jinja2==3.0.3
> MarkupSafe==2.1.5
> packaging==23.2
> Pygments==2.17.2
> PyYAML==6.0.1
> requests==2.31.0
> snowballstemmer==2.2.0
> Sphinx==2.4.4
> sphinxcontrib-applehelp==1.0.4
> sphinxcontrib-devhelp==1.0.2
> sphinxcontrib-htmlhelp==2.0.1
> sphinxcontrib-jsmath==1.0.1
> sphinxcontrib-qthelp==1.0.3
> sphinxcontrib-serializinghtml==1.1.5
> urllib3==2.2.0
>
> My preferred way forward would be to put this in
> Documentation/sphinx/requirements-2.4.4.txt and then update
> Documentation/sphinx/requirements.txt to be completely unconstrained as
> much as possible (just specify the bare minimum set of packages with
> only lower bounds on the versions).
>
> If you agree with the approach, feel free to submit that as a patch (if
> not, I can submit one in the next few days), I just didn't want to snipe
> your contribution.
>

Vegard,

I tried to look into the "completely unconstrained as much as
possible" proposal and looked into what I can reduce in the
sphinx_preinstall. I have just shared the changes here:

https://lore.kernel.org/linux-doc/20240227131410.35269-1-lukas.bulwahn@gmail.com/

Feel free to pick up this patch; I will probably not touch this for a
week now and just see if it works for others or if others will pick it
up.


Best regards,

Lukas

      reply	other threads:[~2024-02-27 13:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26  9:38 [PATCH] docs: freeze some package versions for sphinx virtualenv setup Lukas Bulwahn
2024-02-27  6:56 ` Akira Yokosawa
2024-02-27  8:24   ` Lukas Bulwahn
2024-02-27  8:40     ` Vegard Nossum
2024-02-27 13:17       ` Lukas Bulwahn [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='CAKXUXMzh4hznQNL+K_PrtJ-Ug1p0Q-JGOsTmAt=6fi4d07YOFw@mail.gmail.com' \
    --to=lukas.bulwahn@gmail.com \
    --cc=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=vegard.nossum@oracle.com \
    /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 NNTP newsgroup(s).