From: David Bremner <bremner@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#996151: sphinx-doc: use of definfoenclose generates warnings from makeinfo
Date: Mon, 11 Oct 2021 10:11:42 -0300 [thread overview]
Message-ID: <163395790236.1447749.15123836938967375847.reportbug@convex.cs.unb.ca> (raw)
Package: sphinx-doc
Version: 4.2.0-4
Severity: minor
Tags: upstream
X-Debbugs-Cc: notmuch@notmuchmail.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Notmuch uses sphinx-doc to generate info documenation from rst
documents. Somewhat recently makeinfo has started complaining that
definfoenclose is obsolete. This generates about 40 lines of unhelpful
warnings in building notmuch, so it would be nice to eliminate the
noise.
The texinfo documentation says
In practice, there is little use for this command, and we do not recommend you use it. Support for @definfoenclose may be removed in future releases of Texinfo.
As far as I can tell the use of definfoenclose is coming from texinfo generated by
sphinx/writers/texinfo.py.
- -- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-proposed-updates-debug'), (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sphinx-doc depends on:
ii docutils-doc 0.16+dfsg-4
ii libjs-mathjax 2.7.9+dfsg-1
ii libjs-sphinxdoc 4.2.0-4
ii python-requests-doc 2.25.1+dfsg-2
ii python3-doc 3.9.2-3
sphinx-doc recommends no packages.
sphinx-doc suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmFkOA0ACgkQA0U5G1Wq
FSEt1RAAuKQDDYbgUgQkf7SFCT61hZkdn7nkky8TDdf0uBho0FsG2BfcroQxcdL2
K+DGsWJiUFE851BSo72+1whluGEPxuU34sW05/3TyN8M1MhDcHr8HLJMMDxqfXlL
lfJQBd4cHChEyX1GJrZha5oXlTo3pcL9VsaelYzI9/hRXHx+M8VRZ/x6gx6bdaOl
cYSPyhF9f9DCRJjWoUSHwNADjyofrIAEzCJLfAvVRVTaQWz0vL3PxPYLkK68uz0R
sB81pOWSsY9DUYQHDW5ykQQxj0DLoX9J9mNvQPmOsqyN4yZGQTn1w1yGWxEgb296
+HWU5wL0kKMdDostEjFqKFPIXYcNCQlbJvyqnA+oa72D7l386XfeUSSbi0K9oadu
rJS9Cnn65HslNJDh+BqRbQvYDpH0aWVX7YbNqCPEg32fESs/O7HrHFdYaQ1iI36W
YmyH+vgiIt5LnbLbfvS6t3d5nVpoNHneok+9zRhgL/6eTP3VkcPnsdFvYvNaKC/i
/m9Tb8YsY4KKXDzPja3AmuJrhzPA1fLuk5hfsHQNfF4umMOZ0fU25rOnR07mji44
emKqEcAivYHBd+twnorWRhA+Esw8M0WpDMRIcewg49S6l6mgFkzVB3kYnDQXbTm9
l+DHrNisYs/iPFbdf0p74ZJQbJ/V6lI1GF9jU78Gp30TkcQ/mAM=
=Q/CX
-----END PGP SIGNATURE-----
reply other threads:[~2021-10-11 13:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=163395790236.1447749.15123836938967375847.reportbug@convex.cs.unb.ca \
--to=bremner@debian.org \
--cc=996151@bugs.debian.org \
--cc=submit@bugs.debian.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).