All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Akira Yokosawa <akiyks@gmail.com>
Cc: linux-doc@vger.kernel.org, Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: Error at www.kernel.org/doc/html/next/ since next-20250610
Date: Thu, 19 Jun 2025 13:51:45 -0600	[thread overview]
Message-ID: <87frfvh5m6.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250617-translucent-crouching-poodle-a826e2@lemur>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:

> On Mon, Jun 16, 2025 at 08:18:22PM +0900, Akira Yokosawa wrote:
>> I'm not sure but there might have been some minor incompatibility
>> between past versions of dependencies.
>> 
>> I'd rather upgrade Sphinx to 8.2.3 (latest).
>> 
>> Konstantin, could you try it?
>
> Looks like 8.2.3 requires python-3.11, which I don't have readily
> available on the system that builds the documentation. However,
> upgrading to 7.4 also fixed the problem, so the latest next tree is
> now built and should be propagating shortly.

[Catching up after some much-needed time in the wilderness...]

Konstantin, is there any easy way to get a notification when the build
there fails?  I was entirely unaware of the problem, needless to say.

Once I've dug out a little further, I'll try to figure out why my change
makes things explode.  It really shouldn't...so it should be possible to
find a way to work around the problem and avoid putting in version
requirements (and tests) that we haven't needed so far.

Thanks,

jon

      reply	other threads:[~2025-06-19 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 11:18 Error at www.kernel.org/doc/html/next/ since next-20250610 Akira Yokosawa
2025-06-16 12:05 ` Mauro Carvalho Chehab
2025-06-19  2:22   ` Akira Yokosawa
2025-06-19  6:16     ` Mauro Carvalho Chehab
2025-06-19  6:50       ` Randy Dunlap
2025-06-17 20:29 ` Konstantin Ryabitsev
2025-06-19 19:51   ` Jonathan Corbet [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=87frfvh5m6.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=akiyks@gmail.com \
    --cc=konstantin@linuxfoundation.org \
    --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.