Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
The full build log is available from:
http://qa-logs.debian.net/2025/01/07/jupyter-client_8.6.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250107;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250107&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

The error «(SEVERE/4) Unexpected section title.» is about the Parameters
and Returns headings that are inserted into the API docs (running sphinx
with `-v -v -v` revealed that).

There is on-the-fly manipulation of the docstrings in
jupyter_client/client.py::reqrep - I was able to get the docs to build
by changing the inserted Parameters and Returns into paragraphs rather
than headings. I've attached a patch that does this. I don't think it's
quite the right change to be making, but it might help someone else
understand the problem and find a better solution.

I can't begin to fathom why this is failure is Python 3.13 specific; the
last time this package built on the buildd was with sphinx 7.4, so this
might actually be a change between sphinx 7.4 and 8.1 (although I didn't
spot anything in the changelog), rather than Python 3.12 and 3.13.

Incidentally, the warning that the intersphinx mapping not being found
can be fixed by removing the «file://» from the mapping that is defined
in debian/patches/docs-local-intersphinx.diff; an updated patch for that
one is attached too.

Stuart

Control: tags -1 + patch

An alternative way to fixing this is to remove all the whitespace
indentation in the jupyter_client/client.py::reqrep function. That lets
the build complete with the headings intact... the output seems to be as
intended.

Stuart

Hello,

Bug #1092533 in jupyter-client reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/jupyter-client/-/commit/ed70b04d8720c988890e7f38c776469488d51fc6

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1092533

We believe that the bug you reported is fixed in the latest version of
jupyter-client, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1092533@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julian Gilbey <jdg@debian.org> (supplier of updated jupyter-client package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 13 Jan 2025 20:39:50 +0000
Source: jupyter-client
Architecture: source
Version: 8.6.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+python@tracker.debian.org>
Changed-By: Julian Gilbey <jdg@debian.org>
Closes: 1092533
Changes:
 jupyter-client (8.6.3-2) unstable; urgency=medium
 .
   * Team upload
   * Fix intersphinx error
   * Fix FTBFS in Sphinx documentation building (closes: #1092533)
Checksums-Sha1:
 9d5a45cfb0dc2d982dcf72fcc1e49470bd0b0446 3013 jupyter-client_8.6.3-2.dsc
 08a0d2a5c8af136d50358466d0aa1ff31c3b6a68 10884 jupyter-client_8.6.3-2.debian.tar.xz
 36cc0ce2b4ae7fc347479b5f9e45e4cbbb72a5f2 11894 jupyter-client_8.6.3-2_amd64.buildinfo
Checksums-Sha256:
 3bc97709d10d1c05534685d60641dab3291e701c7bc712948004ecda399894cc 3013 jupyter-client_8.6.3-2.dsc
 91964e300219ef0091acc9d98eeb619a810d50737855bc98fcfd1a189107a1eb 10884 jupyter-client_8.6.3-2.debian.tar.xz
 bf2596821aea6ee6f8d5313a984690756d3c146cbab162cf4fc13cc02420780d 11894 jupyter-client_8.6.3-2_amd64.buildinfo
Files:
 deb1c346ad55ce2975f836c5e69c0a84 3013 python optional jupyter-client_8.6.3-2.dsc
 5167cb9e0bcad65d93e40c5caa1b26e9 10884 python optional jupyter-client_8.6.3-2.debian.tar.xz
 b59e6b1cba7a749b9fc730d45756876b 11894 python optional jupyter-client_8.6.3-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJDBAEBCgAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmeFfiIPHGpkZ0BkZWJp
YW4ub3JnAAoJEGlcQpMWwHv+TSwP/0QYbu+Fmbobde+RPGyX8lu8BGkPIOxmaajK
HgIm0u7L5HjIrN0hIGRFBLtmsI5dHUZ7sQg2FyL80Y4dY6LmCxnv1ilZMCwjKI24
+d40JSCawjFJaVb5RM84/SOvKyoeB4ALn5rD/IE3l9nHTjAQAbmysitRtPg0i4Ge
N/U7zhyql13ujJjCI5sdsOKwfdm6zRbewIHfTvn8BYorkOGO38FyGJkv7HWgA+AE
UAcKGRVs4Wn7HdUchhHLMImNw/ZlfCRXPO+89YmDmwbCMINhsdMAc4eDsuaLsoWA
/4di6JEcOCreSun5dALNo3sPHQ/o0BipQ7/ZpTTYVnOvIpvlOukUQBC8YoyFJaKv
wGXJ2ROsJJtny7XIniQeiSyUawabx0bClJhs6jdU4rks+dYeqaG3h7fAwfQO7t99
spJuwbiJfcDajuhiudgkgTZK82/ky1H0dLeGB5WuHUT1ohhL2FwlLZUf/NauSuNv
0Rawc+3iTDdzTxM+Pk2M7uDk2nxtHndpeZwJlSb4Ugi21GZG4S6d144IIq9naUH9
AwpRtbjMEn8n/ZUkwVHNYRkvotojUCeXn0bXG/clfrVnIQ+4B6vRsxZY3d91TOHf
nLZWtjjiBRJMPTdOJQmu5Al59V265J2SebTCak7DGGHukg/j7FtoJj/zBq02aaYY
5yjM+Lex
=TFdg
-----END PGP SIGNATURE-----

Thanks Stuart!

It's a nice idea, but it messes up the Python < 3.13 docstrings.  I've
found a slightly better fix and submitted it as a PR and uploaded it
to unstable (though I messed up the changelog, so might have to try
again!).

Best wishes,

   Julian