All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-doc@vger.kernel.org
Subject: Re: docs: sphinx: avoid using the deprecated node.set_class()
Date: Fri, 20 Jun 2025 15:05:39 +0200	[thread overview]
Message-ID: <20250620150406.3e2291c2@sal.lan> (raw)
In-Reply-To: <528f0354-1869-4cfe-b71d-fe169b2bfc76@gmail.com>

Em Fri, 20 Jun 2025 20:14:57 +0900
Akira Yokosawa <akiyks@gmail.com> escreveu:

> Mauro!
> 
> On Fri, 20 Jun 2025 09:44:30 +0200, Mauro Carvalho Chehab wrote:
> > Em Fri, 20 Jun 2025 11:22:48 +0900
> > Akira Yokosawa <akiyks@gmail.com> escreveu:
> >   
> [...]
> 
> > 
> > I didn't test it yet, but yesterday I wrote a script which allows us to test
> > for Sphinx version breakages on multiple versions in one go.
> > 
> > Using it (and again before this patch, but after my parser-yaml series), I 
> > noticed that 6.0.1 with "-jauto" with those packages:  
> 
> Why did you pick 6.0.1, which was in the middle of successive releases in
> early 6.x days. 

I added all major,minor,latest-patch version since 3.4.3 and added to
the script. I didn't check what of those are inside a distro or not.

> No distro Sphinx packagers have picked this version.

The hole idea is to have a script where we can automate build tests
with old versions. Perhaps it makes a sense to add a flag at the table
indicating what major distros have what sphinx version and a command
line parameter to either test all or just the ones shipped on major
distros.
> 
> Just see the release history:
> 
> [2022-10-16]  5.3.0  ### stable ###
> [2022-12-29]  6.0.0
> [2023-01-05]  6.0.1
> [2023-01-05]  6.1.0  6.1.1 
> [2023-01-07]  6.1.2
> [2023-01-10]  6.1.3  ### stable ###
> [2023-04-23]  6.2.0
> 
> The crash you observed is hardly related to this fix.

Almost certainly, the breakage with 6.0.1 is unrelated to this
change.

> I'd ignore this report as a random noise.
> My Tested-by: still stands.
> 
> Regards,
> Akira
> 

  reply	other threads:[~2025-06-20 13:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 21:26 docs: sphinx: avoid using the deprecated node.set_class() Jonathan Corbet
2025-06-20  2:22 ` Akira Yokosawa
2025-06-20  7:44   ` Mauro Carvalho Chehab
2025-06-20 11:14     ` Akira Yokosawa
2025-06-20 13:05       ` Mauro Carvalho Chehab [this message]
2025-06-20 18:44         ` Mauro Carvalho Chehab
2025-06-20 19:54           ` Mauro Carvalho Chehab
2025-06-20 13:54   ` Jonathan Corbet
2025-06-20 14:36     ` Akira Yokosawa

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=20250620150406.3e2291c2@sal.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=mchehab@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.