From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] doc: fix documentation build with latest setuptools
Date: Thu, 12 Feb 2026 17:07:32 +0100 [thread overview]
Message-ID: <20260212160732.GA54354@pevik> (raw)
In-Reply-To: <DGCW24NO41YF.34RVLSFL2026H@suse.com>
Hi Andrea,
> > It is a workaround in a sense because new linuxdoc master thanks to my fix [1]
> Now it's more clear, thanks for fixing it!
> > will not need setuptools any more (which I explained in my patch). Normally we
> > would update, but upstream does not have time to release.
> > Also, new release will use hatch, we'll need to use pyproject.toml instead of
> > requirements.txt.
> Isn't pyproject.toml used specifically for python projects? I'm not sure
> about our LTP documentation setup which is just a sphinx configuration.
Likely, my python fu is very limited.
Anyway, because CI started to fail and also our real doc started to fail (Feb 11
and 12) [1] I agreed with Andrea to merge the fix. I dared to add a comment that
it's workaround.
Kind regards,
Petr
[1] https://app.readthedocs.org/projects/linux-test-project/builds/?version__slug=latest
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-02-12 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 16:06 [LTP] [PATCH] doc: fix documentation build with latest setuptools Andrea Cervesato
2026-02-11 16:16 ` Cyril Hrubis
2026-02-12 8:48 ` Petr Vorel
2026-02-12 9:01 ` Andrea Cervesato via ltp
2026-02-12 9:32 ` Petr Vorel
2026-02-12 9:50 ` Andrea Cervesato via ltp
2026-02-12 16:07 ` Petr Vorel [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=20260212160732.GA54354@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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