[Pkg-salt-team] Bug#955057: Bug#955057: salt: FTBFS with Sphinx 2.4: AttributeError: __enter__

Benjamin Drung benjamin.drung at cloud.ionos.com
Mon Mar 30 12:38:24 BST 2020


Am Freitag, den 27.03.2020, 20:58 +0300 schrieb Dmitry Shachnev:
> Hi Benjamin!
> 
> On Fri, Mar 27, 2020 at 06:01:36PM +0100, Benjamin Drung wrote:
> > Thanks for reporting this failure. To troubleshoot, I need the full
> > stack trace that sphinx just saved in /tmp/sphinx-err-r3r4hnih.log.
> > 
> > Is there an easy way to let sphinx print the stack trace instead of
> > storing it? Do you have snippets for the Debian packaging?
> 
> Call sphinx-build with -T option which makes in print the whole
> traceback.
> 
> In your package, you can change these lines in debian/rules
> 
>     HTML_THEME=saltstack make -C doc html
> SPHINXBUILD=/usr/share/sphinx/scripts/python3/sphinx-build
>     HTML_THEME=saltstack make -C doc man
> SPHINXBUILD=/usr/share/sphinx/scripts/python3/sphinx-build
> 
> to
> 
>     HTML_THEME=saltstack make -C doc html
> SPHINXBUILD=/usr/share/sphinx/scripts/python3/sphinx-build
> SPHINXOPTS=-T
>     HTML_THEME=saltstack make -C doc man
> SPHINXBUILD=/usr/share/sphinx/scripts/python3/sphinx-build
> SPHINXOPTS=-T
> 
> Alternatively, you can use -v which implies -T and makes the output
> more
> verbose (which is in line with Policy § 4.9).

Thanks for that help. After adding -T, I got the full stack trace:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/cmd/build.py", line 272, in build_main
    app = Sphinx(args.sourcedir, args.confdir, args.outputdir,
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 272, in __init__                                                                                                                                                  
    self._init_builder()
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 328, in _init_builder
    self.events.emit('builder-inited')
  File "/usr/lib/python3/dist-packages/sphinx/events.py", line 99, in emit
    results.append(callback(self.app, *args))
  File "/usr/lib/python3/dist-packages/sphinx/ext/intersphinx.py", line 233, in load_mappings
    with concurrent.futures.ThreadPoolExecutor() as pool: 
AttributeError: __enter__

It looks like a bug in sphinx, because the full stack trace consists
entirely of code from sphinx itself. I get the same error message when
disabling all extensions from salt (shipped in docs/_ext/).

-- 
Benjamin Drung

DevOps Engineer and Debian & Ubuntu Developer
Platform Integration (IONOS Cloud)

1&1 IONOS SE | Greifswalder Str. 207 | 10405 Berlin | Germany
E-mail: benjamin.drung at cloud.ionos.com | Web: www.ionos.de

Hauptsitz Montabaur, Amtsgericht Montabaur, HRB 24498

Vorstand: Dr. Christian Böing, Hüseyin Dogan, Dr. Martin Endreß, Hans-
Henning Kettler, Arthur Mai, Matthias Steinberg, Achim Weiß
Aufsichtsratsvorsitzender: Markus Kadelke


Member of United Internet

Diese E-Mail kann vertrauliche und/oder gesetzlich geschützte
Informationen enthalten. Wenn Sie nicht der bestimmungsgemäße Adressat
sind oder diese E-Mail irrtümlich erhalten haben, unterrichten Sie
bitte den Absender und vernichten Sie diese E-Mail. Anderen als dem
bestimmungsgemäßen Adressaten ist untersagt, diese E-Mail zu speichern,
weiterzuleiten oder ihren Inhalt auf welche Weise auch immer zu
verwenden.

This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient of this e-mail, you are hereby
notified that saving, distribution or use of the content of this e-mail 
in any way is prohibited. If you have received this e-mail in error,
please notify the sender and delete the e-mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-salt-team/attachments/20200330/6363fe82/attachment.sig>


More information about the pkg-salt-team mailing list