Your message dated Wed, 15 Jul 2026 18:43:40 +0300
with message-id <[email protected]>
and subject line Re: Bug#1135303: sphinx: New version breaks a bunch of packages
has caused the Debian Bug report #1135303,
regarding sphinx: New version breaks a bunch of packages
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1135303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1135303
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:sphinx
Version: 9.1.0-2
Severity: serious
Tags: forky sid ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, many packages using sphinx
do not build from source anymore.
For example, bme280 fails in this way:
Traceback
=========
File
"/usr/lib/python3/dist-packages/sphinx/ext/autodoc/_dynamic/_loader.py", line
204, in _make_props_from_impo
rted_object
_obj___module__=obj.__name__,
^^^^^^^^^^^^
AttributeError: '_const' object has no attribute '__name__'. Did you mean:
'__ne__'?
The full traceback has been saved in:
/tmp/sphinx-err-u1f23xzf.log
Full build log available here:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/bme280_0.2.4-3.rbuild.log.gz
The affected packages are:
src:bme280
src:buildbot
src:fmtlib
src:imath
src:jupyter-server
src:khard
src:libmemcached
src:pythondialog
src:python-odoorpc
src:python-treq
src:python-validate-pyproject
src:sentry-python
src:sphinxcontrib-emojicodes
src:tombo
src:votca
I've triggered rebuilds for all of them in reproducible-builds,
and I expect all of them to fail in similar ways.
This can be either a bug in sphinx, or a bug in the individual packages, but I
don't
really know which one is the case.
If this is a bug in sphinx, please add an "affects" on all the above src
packages, so that
we know that sphinx is the reason we can't currently build them from source.
On the other hand, if this really is a bug in the affected packages, please
clone this
bug as many times as required, reassign to the affected packages, and (if you
can) give
the maintainers some hint about the proper way to fix the issue.
Thanks.
--- End Message ---
--- Begin Message ---
On Sat, May 02, 2026 at 10:52:05AM +0300, Dmitry Shachnev wrote:
> Hi Santiago!
>
> On Sat, May 02, 2026 at 12:33:55AM +0200, Santiago Vila wrote:
> > Ok, I'm going to assume that this is a bug in the affected packages,
> > but I will file the individual reports myself.
>
> Thank you for doing this.
>
> I would also assume that they are bugs in the affected packages. Some of
> them may be bugs in Sphinx, but I searched for some of the errors in the
> upstream bug tracker and did not find anything.
Since the reports for individual packages have been filed, I am closing
this bug.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
--- End Message ---
