Your message dated Wed, 22 Oct 2025 22:11:39 -0500 with message-id <2810299.mvXUDI8C0e@riemann> and subject line Re: ghostscript: FTBFS: sphinx.errors.ExtensionError: Could not import extension rst2pdf.pdfbuilder (exception: No module named 'docutils.utils.roman') has caused the Debian Bug report #1118314, regarding ghostscript: FTBFS: sphinx.errors.ExtensionError: Could not import extension rst2pdf.pdfbuilder (exception: No module named 'docutils.utils.roman') 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 owner@bugs.debian.org immediately.) -- 1118314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118314 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian BTS <submit@bugs.debian.org>
- Subject: ghostscript: FTBFS: sphinx.errors.ExtensionError: Could not import extension rst2pdf.pdfbuilder (exception: No module named 'docutils.utils.roman')
- From: Santiago Vila <sanvila@debian.org>
- Date: Fri, 17 Oct 2025 23:08:36 +0000
- Message-id: <[🔎] E1v9tYq-004cQk-18@paradis.debian.org>
Package: src:ghostscript Version: 10.06.0~dfsg-3 Severity: serious Tags: ftbfs forky sid Dear maintainer: During a rebuild of all packages in unstable, this package failed to build. Below you will find the last part of the build log (probably the most relevant part, but not necessarily). If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202510/ About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages. If you cannot reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and add an affects on src:ghostscript, so that this is still visible in the BTS web page for this package. Thanks. -------------------------------------------------------------------------------- [...] Traceback ========= File "/usr/lib/python3/dist-packages/sphinx/registry.py", line 544, in load_extension raise ExtensionError( __('Could not import extension %s') % extname, err ) from err sphinx.errors.ExtensionError: Could not import extension rst2pdf.pdfbuilder (exception: No module named 'docutils.utils.roman') The full traceback has been saved in: /tmp/sphinx-err-mnxxkpjb.log To report this error to the developers, please open an issue at <https://github.com/sphinx-doc/sphinx/issues/>. Thanks! Please also report this if it was a user error, so that a better error message can be provided next time. make[1]: *** [debian/rules:64: execute_after_dh_auto_build-indep] Error 2 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:43: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
- To: 1118314-done@bugs.debian.org
- Subject: Re: ghostscript: FTBFS: sphinx.errors.ExtensionError: Could not import extension rst2pdf.pdfbuilder (exception: No module named 'docutils.utils.roman')
- From: Steven Robbins <steve@sumost.ca>
- Date: Wed, 22 Oct 2025 22:11:39 -0500
- Message-id: <2810299.mvXUDI8C0e@riemann>
- In-reply-to: <[🔎] E1v9tYq-004cQk-18@paradis.debian.org>
On Fri, 17 Oct 2025 23:08:36 +0000 Santiago Vila <sanvila@debian.org> wrote: > Package: src:ghostscript > Version: 10.06.0~dfsg-3 > Severity: serious > Tags: ftbfs forky sid > > Dear maintainer: > > During a rebuild of all packages in unstable, this package failed to build. I was able to build using pbuilder. > > Below you will find the last part of the build log (probably the most > relevant part, but not necessarily). If required, the full build log > is available here: > > https://people.debian.org/~sanvila/build-logs/202510/ > > About the archive rebuild: The build was made on virtual machines from AWS, > using sbuild and a reduced chroot with only build-essential packages. > > If you cannot reproduce the bug please contact me privately, as I > am willing to provide ssh access to a virtual machine where the bug is > fully reproducible. > > If this is really a bug in one of the build-depends, please use > reassign and add an affects on src:ghostscript, so that this is still > visible in the BTS web page for this package. > > Thanks. > > -------------------------------------------------------------------------------- > [...] > Traceback > ========= > > File "/usr/lib/python3/dist-packages/sphinx/registry.py", line 544, in load_extension > raise ExtensionError( > __('Could not import extension %s') % extname, err > ) from err > sphinx.errors.ExtensionError: Could not import extension rst2pdf.pdfbuilder (exception: No module named 'docutils.utils.roman') > > > The full traceback has been saved in: > /tmp/sphinx-err-mnxxkpjb.log > > To report this error to the developers, please open an issue at <https:// github.com/sphinx-doc/sphinx/issues/>. Thanks! > Please also report this if it was a user error, so that a better error message can be provided next time. > make[1]: *** [debian/rules:64: execute_after_dh_auto_build-indep] Error 2 > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > make: *** [debian/rules:43: binary] Error 2 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 > -------------------------------------------------------------------------------- > > >Attachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---