Bug#882026: qtiplot FTBFS: fatal error: sipAPIqti.h: No such file or directory
Hi Anton! On Sat, Dec 30, 2017 at 05:50:57PM +0100, Anton Gladky wrote: > It looks like sip4_4.19 broke the qtiplot (upload without rebuild of all > reverse dependencies?). sip 4.19 broke qtiplot, but I reported that and it was fixed. See #872636. Looks like this time some minor release of sip broke it (probably 4.19.4). It was a minor release and it was not announced that it can break something, so I did not test the reverse dependencies that time. > Anyway, I have tried to fix this particular part of compilation > process [1]. But it still fails to compile due to major changes in sip. > Help is welcome. Please try this patch: https://bugs.gentoo.org/641514#c2 -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#878369: sfepy: FTBFS: latex_preamble has no effect in Sphinx 1.6
Source: sfepy
Version: 2016.2-3
Severity: serious
Justification: fails to build from source
Tags: patch fixed-upstream
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.6
Dear maintainer,
sfepy package currently uses latex_preamble configuration option to define
its custom LaTeX commands. However that option was deprecated [1] in Sphinx
0.5 (in 2008) and removed [2] in Sphinx 1.6.
This makes the package FTBFS with the following error (\pdiff is defined in
the preamble):
! Undefined control sequence.
l.1018 \Omega \setminus \Gamma\), i.e. \(\pdiff
{T}{\ul{n}} = 0\) there. The
?
! Emergency stop.
A patch to use the modern setting is attached, based on upstream commit [3].
[1]: https://github.com/sphinx-doc/sphinx/commit/f16dae964a7a5298
[2]: http://www.sphinx-doc.org/en/stable/changes.html#features-removed
[3]: https://github.com/sfepy/sfepy/commit/8fb2189c3a9a9aec
--
Dmitry Shachnev
Description: Updated conf.py to new LaTeX customization scheme
Origin: upstream, https://github.com/sfepy/sfepy/commit/8fb2189c3a9a9aec
Last-Update: 2017-10-13
--- a/doc/conf.py
+++ b/doc/conf.py
@@ -214,7 +214,8 @@
# Additional stuff for the LaTeX preamble.
#latex_preamble = ''
-latex_preamble = r"""
+latex_elements = {
+'preamble': r'''
\usepackage{bm}
\usepackage{amsfonts}
\def\dt{{\Delta t}}
@@ -244,7 +245,8 @@
\def\vb{\bm{v}}
\def\Mb{\bm{M}}
\def\vphib{\bm{\varphi}}
-"""
+''',
+}
# LS: Are the following needed as well?
#\def\Vcal{\mathcal{V}}
#\def\Tcal{\mathcal{T}}
@@ -258,7 +260,7 @@
#latex_use_modindex = True
# Preamble for pngmath images
-pngmath_latex_preamble = latex_preamble
+pngmath_latex_preamble = latex_elements['preamble']
# Turn off numpydoc autosummary tables
numpydoc_show_class_members = False
signature.asc
Description: PGP signature
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#877109: pybtex FTBFS with Sphinx 1.6.4-1
Control: forwarded -1 https://bitbucket.org/pybtex-devs/pybtex/pull-requests/9/ Hi Ghislain, On Sat, Sep 30, 2017 at 10:40:52AM +0100, Ghislain Vaillant wrote: > And what the hell am I supposed to do with this?! > > Nice of you to report the issue but, without further context, I can't take > further actions. > > Isn't it the Dmitry's responsibility to at least communicate on the change > and suggest solutions for it to people impacted by RCs? If he did, please > point me to the announcement in case I missed it. Sorry for that. I was aware of 5 or 6 packages that my change could affect, but I did not expect that there would be more of them. Also I do not have the resources to rebuild all reverse dependencies for every change in Sphinx. Anyway, better late than never, so let me explain what happened there: * Sphinx has a JavaScript library (doctools.js) that it uses to perform search on built HTML documents. This library is loaded from search.html page, and that page should contain a DOCUMENTATION_OPTIONS JavaScript object which acts like configuration for that library. * Right now, if you open /usr/share/doc/python-pybtex-doc/html/search.html from your package, you will notice that search does not work. The browser console will have an error like this: searchtools.js:543:96: TypeError: suffix is undefined It is not something that I broke; it is caused by a change in Sphinx 1.5, that added one more required option (SOURCELINK_SUFFIX) which should be in DOCUMENTATION_OPTIONS. * Good news is that you should not notice such issues yourself; dh_sphinxdoc performs the sanity check for you. It had a warning about this since sphinx 1.5.2-2. In the latest upload I turned this warning into error, which is why you get this FTBFS bug. * The only packages affected by this are ones that have custom templates, that do not inherit from sphinx/themes/basic/layout.html. Yours has one in docs/theme/layout.html. * I have just created an upstream pull request which fixes this issue. You can grab the patch from there. In future, please CC me if you want to complain about Sphinx. -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#784464: Qt4 WebKit removal: raising severity to serious
Control: severity -1 serious Dear maintainer(s), As recently announced [1], we are going to remove not only Qt 4 WebKit, but Qt 4 as a whole in Buster. As removing Qt 4 WebKit is the first step, I am raising the severity of this bug to serious. Please port your package to Qt 5 if you do not want to get it removed from Debian. In Qt 5, the WebKit module is supported, and we are currently preparing a major update based on 5.212 branch [2]. [1]: https://lists.debian.org/debian-devel-announce/2017/08/msg6.html [2]: https://code.qt.io/cgit/qt/qtwebkit.git/log/?h=5.212 -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#872636: qtiplot: FTBFS with sip 4.19: 'sipType_QDateTime' was not declared in this scope
Control: tags -1 +patch
On Sat, Aug 19, 2017 at 06:27:08PM +0300, Dmitry Shachnev wrote:
> Dear maintainer,
>
> qtiplot fails to build with sip 4.19.3 and python-qt4 4.12.1, both of which
> are available in experimental:
>
> src/scripting/qti.sip: In function ‘int setCellDataHelper(Table*, int, int,
> PyObject*)’:
> src/scripting/qti.sip:151:35: error: ‘sipType_QDateTime’ was not declared
> in this scope
>if (sipCanConvertToType(item, sipType_QDateTime, 0)) {
> ^
> src/scripting/qti.sip:167:35: error: ‘sipType_QTime’ was not declared in
> this scope
>if (sipCanConvertToType(item, sipType_QTime, 0)) {
> ^
Gentoo has applied this patch to fix the failure:
https://bugs.gentoo.org/show_bug.cgi?id=609280#c1
--
Dmitry Shachnev
signature.asc
Description: PGP signature
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#872314: pytables: FTBFS with Sphinx 1.6: Needs build-dep on latexmk
Source: pytables Version: 3.3.0-5 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.6 Dear maintainer, pytables fails to build with Sphinx 1.6, currently available in experimental: /usr/bin/make -C build/latex all-pdf make[3]: Entering directory '/build/pytables-3.3.0/doc/build/latex' latexmk -pdf -dvi- -ps- 'usersguide-3.3.0.tex' make[3]: latexmk: Command not found Makefile:33: recipe for target 'usersguide-3.3.0.pdf' failed make[3]: *** [usersguide-3.3.0.pdf] Error 127 Since Sphinx 1.6, latexmk is required to build the LaTeX documentation [1]. Adding a build-dependency on latexmk should help. [1]: https://github.com/sphinx-doc/sphinx/pull/3082 -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#872259: sagemath: FTBFS with Sphinx 1.6: TypeError: frompickle() takes exactly 3 arguments (4 given)
Source: sagemath Version: 7.6-3 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.6 Dear maintainer, sagemath fails to build with Sphinx 1.6, currently available in experimental: [dochtml] Building reference manual, first pass. [dochtml] [dochtml] Error building the documentation. [dochtml] Traceback (most recent call last): [...] [dochtml] File "/<>/debian/build/usr/lib/python2.7/dist-packages/sage_setup/docbuild/__init__.py", line 510, in _wrapper [dochtml] build_many(build_ref_doc, L) [dochtml] File "/<>/debian/build/usr/lib/python2.7/dist-packages/sage_setup/docbuild/__init__.py", line 266, in build_many [dochtml] results.append(target(arg)) [dochtml] File "/<>/debian/build/usr/lib/python2.7/dist-packages/sage_setup/docbuild/__init__.py", line 70, in build_ref_doc [dochtml] getattr(ReferenceSubBuilder(doc, lang), format)(*args, **kwds) [dochtml] File "/<>/debian/build/usr/lib/python2.7/dist-packages/sage_setup/docbuild/__init__.py", line 705, in _wrapper [dochtml] for module_name in self.get_modified_modules(): [dochtml] File "/<>/debian/build/usr/lib/python2.7/dist-packages/sage_setup/docbuild/__init__.py", line 834, in get_modified_modules [dochtml] env = self.get_sphinx_environment() [dochtml] File "/<>/debian/build/usr/lib/python2.7/dist-packages/sage_setup/docbuild/__init__.py", line 779, in get_sphinx_environment [dochtml] env = BuildEnvironment.frompickle(self.dir, config, env_pickle) [dochtml] TypeError: frompickle() takes exactly 3 arguments (4 given) Makefile:1093: recipe for target 'doc-html' failed This looks like a result of upstream commit [1], where the signature of frompickle method changed from: def frompickle(cls, srcdir, config, filename): to: def frompickle(cls, filename, app): The full build log is available at [2] (it is from Ubuntu, but there should be no difference with Debian). [1]: https://github.com/sphinx-doc/sphinx/commit/c7bec75bcd12530a [2]: https://launchpadlibrarian.net/17873/buildlog_ubuntu-artful-amd64.sagemath_7.6-3ubuntu3_BUILDING.txt.gz -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#872248: sfepy: FTBFS with Sphinx 1.6: Needs build-dep on latexmk
Source: sfepy Version: 2016.2-2 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.6 Dear maintainer, sfepy fails to build with Sphinx 1.6, currently available in experimental: running pdfdocs make[3]: Entering directory '/<>/doc' PYTHONPATH=.. sphinx-build -b latex -d _build/doctrees . _build/latex Running Sphinx v1.6.3 [...] Build finished; the LaTeX files are in _build/latex. Run `make all-pdf' or `make all-ps' in that directory to run these through (pdf)latex. make[3]: Leaving directory '/<>/doc' make[3]: Entering directory '/<>/doc/_build/latex' latexmk -pdf -dvi- -ps- 'SfePy.tex' make[3]: latexmk: Command not found Makefile:33: recipe for target 'SfePy.pdf' failed make[3]: *** [SfePy.pdf] Error 127 Since Sphinx 1.6, latexmk is required to build the LaTeX documentation [1]. Adding a build-dependency on latexmk should help. [1]: https://github.com/sphinx-doc/sphinx/pull/3082 -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#872239: numexpr: Debug packages should not be removed
Source: numexpr Version: 2.6.2-1 Severity: serious Justification: makes pytables FTBFS Control: affects -1 src:pytables Dear maintainer, The changelog for numexpr 2.6.2-1 says: numexpr (2.6.2-1) unstable; urgency=medium [...] * Drop -dbg package declaration (now debug packages are automatically generated) This is not true. The automatically generated dbgsym packages only contain the debugging symbols for the C extension files. However, the former -dbg packages contained the extensions built for Python debug interpreter: $ dpkg -L python3-numexpr-dbg /usr/lib/python3/dist-packages/numexpr/interpreter.cpython-35dm-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/numexpr/interpreter.cpython-36dm-x86_64-linux-gnu.so [...] These files are needed when you want to use numexpr with the debug interpreter, i.e. /usr/bin/python3-dbg; and they are not present in the automatic dbgsym packages. So please revert dropping the -dbg packages. This was also discussed on debian-python mailing list several times, i.e.: https://lists.debian.org/debian-python/2016/04/msg00093.html I am setting the severity to serious to prevent the new upload from migrating to testing; please feel free to downgrade it if you want. -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#872170: cvxopt: FTBFS with Sphinx 1.6: Needs build-dep on latexmk
Source: cvxopt Version: 1.1.9+dfsg-1 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.6 Dear maintainer, cvxopt fails to build with Sphinx 1.6, currently available in experimental: make --directory=doc/build/latex all-pdf make[2]: Entering directory '/<>/cvxopt-1.1.9+dfsg/doc/build/latex' latexmk -pdf -dvi- -ps- 'CVXOPT.tex' make[2]: latexmk: Command not found Makefile:33: recipe for target 'CVXOPT.pdf' failed make[2]: *** [CVXOPT.pdf] Error 127 Since Sphinx 1.6, latexmk is required to build the LaTeX documentation [1]. Adding a build-dependency on latexmk should help. [1]: https://github.com/sphinx-doc/sphinx/pull/3082 -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#867496: morse-simulator: FTBFS with Sphinx 1.5: ImportError: No module named 'version'
Source: morse-simulator
Version: 1.4-2
Severity: important
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.5
Dear maintainer,
I am about to upload Sphinx 1.5 to unstable (it has been available in
experimental for several months now).
Your package fails to build with it:
Running Sphinx v1.5.6
making output directory...
Exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sphinx/cmdline.py", line 295, in main
opts.warningiserror, opts.tags, opts.verbosity, opts.jobs)
File "/usr/lib/python3/dist-packages/sphinx/application.py", line 163, in
__init__
confoverrides or {}, self.tags)
File "/usr/lib/python3/dist-packages/sphinx/config.py", line 134, in
__init__
execfile_(filename, config)
File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line 129, in
execfile_
exec_(code, _globals)
File "conf.py", line 15, in
ImportError: No module named 'version'
The full build log is attached.
--
Dmitry Shachnev
dpkg-buildpackage -rfakeroot -us -uc -j4
dpkg-buildpackage: warning: using a gain-root-command while being root
dpkg-buildpackage: info: source package morse-simulator
dpkg-buildpackage: info: source version 1.4-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Sylvestre Ledru
dpkg-source --before-build morse-simulator-1.4
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh clean --with python3
dh: Compatibility levels before 9 are deprecated (level 8 in use)
dh_testdir
dh_auto_clean
dh_auto_clean: Compatibility levels before 9 are deprecated (level 8 in use)
dh_clean
dh_clean: Compatibility levels before 9 are deprecated (level 8 in use)
dpkg-source -b morse-simulator-1.4
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building morse-simulator using existing
./morse-simulator_1.4.orig.tar.gz
dpkg-source: info: building morse-simulator in
morse-simulator_1.4-2.debian.tar.xz
dpkg-source: info: building morse-simulator in morse-simulator_1.4-2.dsc
debian/rules build
dh build --with python3
dh: Compatibility levels before 9 are deprecated (level 8 in use)
dh_testdir
dh_update_autotools_config
debian/rules override_dh_auto_configure
make[1]: Entering directory '/morse-simulator-1.4'
dh_auto_configure -- -DBUILD_DOC_SUPPORT=ON
-DPYTHON_EXECUTABLE=/usr/bin/python3 \
-DCPACK_DEBIAN_PACKAGE_DEPENDS=python3-all-dev -DPYMORSE_SUPPORT=ON
dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in use)
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DBUILD_DOC_SUPPORT=ON
-DPYTHON_EXECUTABLE=/usr/bin/python3
-DCPACK_DEBIAN_PACKAGE_DEPENDS=python3-all-dev -DPYMORSE_SUPPORT=ON
-- The C compiler identification is GNU 7.1.0
-- The CXX compiler identification is GNU 7.1.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29")
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.5.3",
required is "3.3")
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.5m.so (found suitable
exact version "3.5")
-- will install python files in /usr/lib/python3/dist-packages
-- Configuring done
-- Generating done
CMake Warning:
Manually-specified variables were not used by the project:
CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_SYSCONFDIR
CPACK_DEBIAN_PACKAGE_DEPENDS
-- Build files have been written to: /morse-simulator-1.4/obj-x86_64-linux-gnu
make[1]: Leaving directory '/morse-simulator-1.4'
dh_auto_build
dh_auto_build: Compatibility levels before 9 are deprecated (level 8 in use)
make -j1
make[1]: Entering directory '/morse-simulator-1.4/obj-x86_64-linux-gnu'
/usr/bin/cmake -H/morse-simulator-1.4
-B/morse-simulator-1.4/obj-x86_64-linux-gnu --check-build-system
CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start
/morse-simulator-1.4/obj-x86_64-linux-gnu/CMakeFiles
/morse-simulator-1.4/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/morse-simulator-1.4/obj-x86_64-linux-gnu'
make -f CMakeFiles/man.dir/build.make CMakeFiles/man.dir/depend
make[3]: Entering directory '/m
Bug#866166: sagemath: FTBFS with Sphinx 1.5: AttributeError: 'BuildEnvironment' object has no attribute 'citations'
Hi Ximin! On Tue, Jul 04, 2017 at 07:35:00AM +, Ximin Luo wrote: > I fixed our other issue in git and now I'm seeing these sphinxdoc errors: > > [..] > make[1]: Entering directory '/home/infinity0/var/lib/sage/sagemath' > dh_sphinxdoc -XMathJax.js -Xtranslations.js -Xsearchtools.js > dh_sphinxdoc: ignoring unknown JavaScript code: > debian/sagemath-doc-ca/usr/share/doc/sagemath/html/ca/intro/_static/thebe-sage.js > [..] > dh_sphinxdoc: > debian/sagemath-doc-en/usr/share/doc/sagemath/html/en/reference/_sources/lie_algebras.rst.txt > is missing > debian/rules:199: recipe for target 'override_dh_sphinxdoc' failed > make[1]: *** [override_dh_sphinxdoc] Error 2 > > Dmitry, if we need to further patch Sphinx or Sage, I'd be happy to do that. > But what exactly is needed? I'm not sure if I totally understood the ticket > you linked: > > https://github.com/sphinx-doc/sphinx/pull/2454 > > Do we just need to put the equivalent of this: > > https://github.com/mitya57/matplotlib/commit/53e6bc46d2f010f9a80e0c73dceb6166705f608f > > into Sage's layout templates? No, the problem is not in the templates, the problem is with installation layout. dh_sphinxdoc (and searchtools.js) expect to to find the source files with the following scheme: .../_sources/ + original filename (i.e. lie_algebras.rst) + sourcelink_suffix if it is different from the original extension (i.e. .txt). Here it fails to find these files. Most probably they are installed without the sourcelink_suffix, i.e. .../_sources/lie_algebras.rst instead of .../_sources/lie_algebras.rst.txt. It looks like it installs using custom code in docbuild/ext/multidocs.py, not by enabling the standard Sphinx’ html_copy_source configuration option. Unfortunately I cannot test sagemath build locally because it exceeds my RAM, but I can suggest two ways to potentially fix it: * Add sourcelink_suffix support to multidocs.py (the “# Setup source symbolic links” block). It can be obtained from app.config.html_sourcelink_suffix. * Or set html_sourcelink_suffix to '.rst' in conf.py. This way it should be the same as original extensions, so dh_sphinxdoc will not try to append it. -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#867026: xtensor-python: Autopkgtest fails with multiple supported Python 3 versions
Source: xtensor-python Version: 0.12.1-1 Dear maintainer, The current test logic in xtensor-python looks like this: for py in $(py3versions -r 2>/dev/null); do cd "$AUTOPKGTEST_TMP"; mkdir build && cd build; ... done When py3versions returns two versions (like in the current sid, where we have Python 3.5 and 3.6), it fails with: mkdir: cannot create directory ‘build’: File exists You need to either use ‘mkdir -p’, or ‘rm -rf build’ before creating it. -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#866166: sagemath: FTBFS with Sphinx 1.5: AttributeError: 'BuildEnvironment' object has no attribute 'citations'
Hi Tobias, and thanks for the quick response! On Wed, Jun 28, 2017 at 02:44:23PM +0100, Tobias Hansen wrote: > Hi Dmitry, > > would it be an option to upload sphinx 1.5 to unstable together with > sagemath 8.0 (which works fine with sphinx 1.5) or do you want to do it > before? We plan to upload sagemath 8.0 to unstable when it's released > (they are at beta12 now). That depends on how long do you estimate the final release to take. From what I found [1] the sage-8.0 milestone still has 341 active issues, which does not sound very optimistic. I can wait for 2 or 3 weeks, but I do not want to wait longer. After all upstream already released Sphinx 1.6 so we are two major releases behind. > Otherwise it's a matter of backporting commits from sagemath 8.0 to 7.6. I think this is not enough, unless the second part of my bugreport is also addressed upstream. [1]: https://trac.sagemath.org/milestone/sage-8.0 -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#866166: sagemath: FTBFS with Sphinx 1.5: AttributeError: 'BuildEnvironment' object has no attribute 'citations'
Source: sagemath Version: 7.6-2 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.5 Dear maintainer, Sagemath fails to build with Sphinx 1.5 (available in experimental, but pending upload to unstable): # Sometimes, parts of the docbuild fail with MemoryError or OSError but # Sage doesn't detect this. Here we detect it and fail the build if so. ! grep Error sage/logs/dochtml.log AttributeError: 'BuildEnvironment' object has no attribute 'citations' WARNING: intersphinx inventory '/<>/debian/build/usr/share/doc/sagemath/inventory/en/reference/objects.inv' not fetchable due to : [Errno 2] No such file or directory: '/<>/debian/build/usr/share/doc/sagemath/inventory/en/reference/objects.inv' AttributeError: 'BuildEnvironment' object has no attribute 'citations' (repeats multiple times) debian/rules:90: recipe for target 'check-dochtml-log' failed This can be fixed by backporting upstream commit [1], but then it fails with dh_sphinxdoc error: debian/rules override_dh_sphinxdoc make[1]: Entering directory '/<>' dh_sphinxdoc -XMathJax.js -Xtranslations.js -Xsearchtools.js dh_sphinxdoc: ignoring unknown JavaScript code: debian/sagemath-doc-ca/usr/share/doc/sagemath/html/ca/intro/_static/mathjax_sage.js dh_sphinxdoc: ignoring unknown JavaScript code: debian/sagemath-doc-ca/usr/share/doc/sagemath/html/ca/intro/_static/thebe-sage.js (more harmless warnings) dh_sphinxdoc: debian/sagemath-doc-en/usr/share/doc/sagemath/html/en/reference/_sources/sage/algebras/affine_nil_temperley_lieb.rst.txt is missing debian/rules:192: recipe for target 'override_dh_sphinxdoc' failed This is most probably related to a change in Sphinx [2], which changed how searchtools.js looks for source files. dh_sphinxdoc now follows the same logic and expects to find these files in their new locations. [1]: https://github.com/sagemath/sage/commit/78e671810360d3e0 [2]: https://github.com/sphinx-doc/sphinx/pull/2454 -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#857816: fityk: broken symlink: /usr/share/fityk/html/_static/websupport.js -> ../../../javascript/sphinxdoc/1.0/websupport.js
Control: affects 857510 - fityk
Control: tags -1 + patch
On Wed, Mar 15, 2017 at 01:32:20PM +0100, Andreas Beckmann wrote:
> On 2017-03-15 11:33, Dmitry Shachnev wrote:
> > This package is not using dh_sphinxdoc, but it is rather linking the files
> > manually (and wrongly), therefore it is not a bug in sphinx.
>
> Thanks for this analysis. It's the same problem in fityk, which also
> doesn't use dh_sphinxdoc ... so cloning the bug accordingly.
>
> 0m42.2s ERROR: FAIL: Broken symlinks:
> /usr/share/fityk/html/_static/websupport.js ->
> ../../../javascript/sphinxdoc/1.0/websupport.js
Attaching a patch for fityk.
--
Dmitry Shachnev
diff -ruN a/debian/control b/debian/control
--- a/debian/control 2017-03-15 15:55:39.0 +0300
+++ b/debian/control 2017-03-15 15:56:14.0 +0300
@@ -34,7 +34,7 @@
Recommends:
gnuplot
Suggests:
- libjs-sphinxdoc
+ ${sphinxdoc:Depends}
Description: general-purpose nonlinear curve fitting and data analysis
Fityk is a flexible and portable program for nonlinear fitting of analytical
functions (especially peak-shaped) to data (usually experimental data). In
diff -ruN a/debian/links b/debian/links
--- a/debian/links 2017-03-15 15:55:39.0 +0300
+++ b/debian/links 2017-03-15 15:56:54.0 +0300
@@ -1,8 +1,3 @@
usr/share/fityk/html usr/share/doc/fityk/html
usr/share/fityk/samplesusr/share/doc/fityk/examples
-usr/share/javascript/sphinxdoc/1.0/doctools.js usr/share/fityk/html/_static/doctools.js
-usr/share/javascript/sphinxdoc/1.0/jquery.js usr/share/fityk/html/_static/jquery.js
-usr/share/javascript/sphinxdoc/1.0/searchtools.js usr/share/fityk/html/_static/searchtools.js
-usr/share/javascript/sphinxdoc/1.0/underscore.js usr/share/fityk/html/_static/underscore.js
-usr/share/javascript/sphinxdoc/1.0/websupport.js usr/share/fityk/html/_static/websupport.js
usr/share/man/man1/fityk.1.gz usr/share/man/man1/cfityk.1.gz
diff -ruN a/debian/rules b/debian/rules
--- a/debian/rules 2017-03-15 15:55:39.0 +0300
+++ b/debian/rules 2017-03-15 16:00:23.0 +0300
@@ -3,7 +3,7 @@
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
%:
- dh $@ --buildsystem=autoconf --parallel
+ dh $@ --buildsystem=autoconf --parallel --with sphinxdoc
override_dh_auto_configure:
dh_auto_configure -- --disable-shared --enable-static
@@ -23,3 +23,6 @@
override_dh_compress:
dh_compress --exclude=.dat --exclude=.fit
+
+override_dh_sphinxdoc:
+ dh_sphinxdoc usr/share/fityk/html
signature.asc
Description: PGP signature
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#844601: python-spyder: "from spyder.plugins.editor import Editor" hangs the machine
On Sun, Nov 27, 2016 at 06:22:52PM +, PICCA Frederic-Emmanuel wrote: > > In other words: if you want to use Qt you *need* a QApplication instance. > > That's Qt basics. Not using it is a bug. > > I understand, > > Nervertheless I think that the python binding should fail gracefully with > an exception instead of segfaulting... PyQt is just a binding, handling segfaults in underlying code is not its responsibility. Moreover, it cannot distinguish segfaults because of missing QApplication from other kinds of segfaults. -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#844601: python-spyder: "from spyder.plugins.editor import Editor" hangs the machine
Hi,
On Sun, Nov 27, 2016 at 03:16:36PM +, PICCA Frederic-Emmanuel wrote:
> > The QFontDatabase method will definitely not work properly without a
> > Q(Gui)Application instance.
>
> thanks for this analyze.
>
> so if I understand correctly, the problem is in the QFontDatabse method
> which should raise an exception instead of segfaulting.
>
> right ?
>
> so I should clone this bug and assign it to python{3}-pyqt5
> sice it is a segfault maybe the culprite is around sip...
No. This has nothing to do with PyQt5. The C++ code using Qt Gui classes
without a Q(Gui)Application will also crash. That is an expected behavior.
Such code should not be run on module *import* time, it should be run
when the spyder code is first *used*.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#844601: python-spyder: "from spyder.plugins.editor import Editor" hangs the machine
Hi all, and sorry for the late response. On Sat, Nov 19, 2016 at 11:48:51AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > I'm CCing the pyqt5 maintainer and expert. Python is not my realm really. The problem with python-spyder is that it tries to use Qt widgets without a QApplication instance. If I construct a QApplication, and then try to import the editor module, it works fine. I think the Python traceback is more helpful here than a C++ stack trace: $ python3 -X faulthandler -c "import spyder.plugins.editor" Fatal Python error: Segmentation fault Current thread 0x7f56650a9700 (most recent call first): File "/usr/lib/python3/dist-packages/qtawesome/iconic_font.py", line 200 in load_font File "/usr/lib/python3/dist-packages/qtawesome/iconic_font.py", line 168 in __init__ File "/usr/lib/python3/dist-packages/qtawesome/__init__.py", line 36 in _instance File "/usr/lib/python3/dist-packages/qtawesome/__init__.py", line 153 in load_font File "/usr/lib/python3/dist-packages/spyder/utils/icon_manager.py", line 257 in icon File "/usr/lib/python3/dist-packages/spyder/plugins/runconfig.py", line 445 in RunConfigPage File "/usr/lib/python3/dist-packages/spyder/plugins/runconfig.py", line 440 in [...] Line 200 of iconic_font.py is: id_ = QFontDatabase.addApplicationFont(os.path.join(directory, ttf_filename)) The QFontDatabase method will definitely not work properly without a Q(Gui)Application instance. -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#816800: [gazebo] Qt4's WebKit removal
Source: gazebo Version: 7.0.0+dfsg-1 User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Hi! As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] <https://lists.debian.org/debian-devel-announce/2015/05/msg1.html> Basically we are about to get the last Qt4 point release and upstream is migrating from WebKit to Blink in the Qt5 series, so we won't have much upstreams support for maintaining Qt4's WebKit (Qt5's WebKit is expected to stay supported until Qt6). In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html If you have any questions, please reply to this mail and CC me. On behalf of the Qt4 maintainers, -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#784613: Bug#784513: qtwebkit removal from python-qt4
Control: severity -1 serious On Mon, Dec 07, 2015 at 09:31:42PM +0300, Dmitry Shachnev wrote: > Hi all, > > I am going to remove qtwebkit support from python-qt4 package in an upload in > early 2015 (but not before January 7th, one month from now). > > Please port your packages before that date, or these bugs will become RC. As promised, this bug is now release-critical. A new python-qt4 upload with removed QtWebKit module will happen shortly. -- Dmitry Shachnev signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#784613: qtwebkit removal from python-qt4
Hi all, I am going to remove qtwebkit support from python-qt4 package in an upload in early 2015 (but not before January 7th, one month from now). That means that these files will be no longer installed (and accompanying documentation files): In python-qt4: - /usr/lib/python2.7/dist-packages/PyQt4/QtWebKit.so - /usr/lib/python2.7/dist-packages/PyQt4/uic/widget-plugins/qtwebkit.py In python-qt4-dbg: - /usr/lib/debug/usr/lib/python2.7/dist-packages/PyQt4/QtWebKit.so - /usr/lib/python2.7/dist-packages/PyQt4/QtWebKit_d.so In python3-pyqt4: - /usr/lib/python3/dist-packages/PyQt4/QtWebKit.cpython-*-*.so - /usr/lib/python3/dist-packages/PyQt4/uic/widget-plugins/qtwebkit.py In python3-pyqt4-dbg: - /usr/lib/debug/usr/lib/python3/dist-packages/PyQt4/QtWebKit.cpython-*-*.so - /usr/lib/python3/dist-packages/PyQt4/QtWebKit.cpython-*-*.so Please port your packages before that date, or these bugs will become RC. The recommended way is to port packages to PyQt5, see the instructions at [1]. For the reasoning behind qtwebkit removal, please see the original bug report and the announcement in [2]. [1]: http://pyqt.sourceforge.net/Docs/PyQt5/pyqt4_differences.html [2]: https://lists.debian.org/debian-devel-announce/2015/05/msg1.html On behalf of python-qt4 maintainers, -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#792711: morse-simulator: FTBFS with Sphinx 1.3: TemplateNotFound: default/layout.html
On Fri, 17 Jul 2015 20:20:22 +0300, Dmitry Shachnev wrote:
> morse-simulator FTBFS with Sphinx 1.3 (which is available in experimental)
>
> The 'default' theme has been renamed to 'classic', so the template file
> is now classic/layout.html.
Sphinx 1.3 is now in unstable, so I bumped the severity to serious.
I have attached the minimal debdiff that fixes the build faulure.
--
Dmitry Shachnevdiff -ruN a/debian/changelog b/debian/changelog
--- a/debian/changelog 2015-04-27 19:57:10.0 +0300
+++ b/debian/changelog 2015-08-15 21:58:32.0 +0300
@@ -1,3 +1,10 @@
+morse-simulator (1.2.2-2) UNRELEASED; urgency=medium
+
+ * Update morse-theme for Sphinx 1.3 (closes: #792711).
+- Bump python3-sphinx build-dependency.
+
+ -- Dmitry Shachnev Sat, 15 Aug 2015 21:57:29 +0300
+
morse-simulator (1.2.2-1) unstable; urgency=medium
* Upload to unstable
diff -ruN a/debian/control b/debian/control
--- a/debian/control 2014-12-30 15:34:42.0 +0300
+++ b/debian/control 2015-08-15 21:57:20.0 +0300
@@ -4,7 +4,7 @@
Maintainer: Debian Science Team
Uploaders: Sylvestre Ledru , Séverin Lemaignan
Build-Depends: debhelper (>= 8.0.0), cmake, python3-dev,
- python3-sphinx, pkg-config, python-concurrent.futures
+ python3-sphinx (>= 1.3), pkg-config, python-concurrent.futures
Standards-Version: 3.9.6
Homepage: http://morse.openrobots.org/
X-Python3-Version: >= 3.2
diff -ruN a/debian/patches/series b/debian/patches/series
--- a/debian/patches/series 2014-12-30 15:32:58.0 +0300
+++ b/debian/patches/series 2015-08-15 21:55:20.0 +0300
@@ -0,0 +1 @@
+sphinx13_theme_rename.diff
diff -ruN a/debian/patches/sphinx13_theme_rename.diff b/debian/patches/sphinx13_theme_rename.diff
--- a/debian/patches/sphinx13_theme_rename.diff 1970-01-01 03:00:00.0 +0300
+++ b/debian/patches/sphinx13_theme_rename.diff 2015-08-15 21:57:09.0 +0300
@@ -0,0 +1,17 @@
+Description: update base template for Sphinx 1.3
+ The 'default' theme has been renamed to 'classic' in Sphinx 1.3.
+Author: Dmitry Shachnev
+Forwarded: no
+Last-Update: 2015-08-15
+
+--- a/doc/morse-theme/templates/layout.html
b/doc/morse-theme/templates/layout.html
+@@ -1,7 +1,7 @@
+ {#
+ MORSE Sphinx template
+ #}
+-{% extends "default/layout.html" %}
++{% extends "classic/layout.html" %}
+
+ {% block rootrellink %}
+ {{ project }}{{ reldelim1 }}
signature.asc
Description: OpenPGP digital signature
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#792726: sympy: FTBFS with Sphinx 1.3: Undefined control sequence \addto
Source: sympy
Version: 0.7.6-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.3
sympy FTBFS with Sphinx 1.3 (which is available in experimental):
make[2]: Entering directory '/tmp/buildd/sympy-0.7.5/doc/_build/latex'
xelatex 'sympy-0.7.5.tex'
[...]
! Undefined control sequence.
l.23 \addto
\captionsenglish{\renewcommand{\figurename}{Fig. }}
?
! Emergency stop.
[...]
Makefile:58: recipe for target 'sympy-0.7.5.pdf' failed
Command addto is defined in babel module, which you seem to be disabling
in doc/src/conf.py.
This looks similar to https://github.com/sphinx-doc/sphinx/issues/1923,
so I have just left a comment there.
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#792711: morse-simulator: FTBFS with Sphinx 1.3: TemplateNotFound: default/layout.html
Source: morse-simulator
Version: 1.2.2-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.3
morse-simulator FTBFS with Sphinx 1.3 (which is available in experimental):
Exception occurred:
File "/tmp/morse-simulator-1.2.2/doc/morse-theme/templates/layout.html",
line 4, in
{% extends "default/layout.html" %}
File "/usr/lib/python3/dist-packages/sphinx/jinja2glue.py", line 159, in
get_source
raise TemplateNotFound(template)
jinja2.exceptions.TemplateNotFound: default/layout.html
CMakeFiles/doc.dir/build.make:52: recipe for target 'CMakeFiles/doc' failed
The 'default' theme has been renamed to 'classic', so the template file
is now classic/layout.html.
Unfortunately there is no easy solution that will work with both Sphinx 1.2
and 1.3, but you can try to base the template on 'basic/layout.html'
(classic extends basic) and embed the parts you need directly into your
template.
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#784613: [spyder] Qt4's WebKit removal
Source: spyder Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Control: block 784513 by -1 Hi! As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. Your package seems to be using it via PyQt4's QtWebKit module. [announce] <https://lists.debian.org/debian-devel-announce/2015/05/msg1.html> Basically we are about to get the last Qt4 point release and upstream is migrating from WebKit to Blink in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit (Qt5's WebKit is expected to stay supported until Qt6). In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5/PyQt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] and the PyQt4 vs PyQt5 differences page [pyqtchanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html [pyqtchanges] http://pyqt.sourceforge.net/Docs/PyQt5/pyqt4_differences.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org. -- Dmitry Shachnev, on behalf of the Qt4 and PyQt4 maintainers -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
