Package: src:macaulay2-jupyter-kernel Version: 0.6.7~beta-3 Severity: serious Tags: ftbfs forky sid
Dear maintainer: During a rebuild of all packages in unstable, your package failed to build. Below you will find how the build ends (probably the most relevant part, but not necessarily). If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202509/ 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 could not 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:macaulay2-jupyter-kernel, so that this is still visible in the BTS web page for this package. Thanks. -------------------------------------------------------------------------------- [...] debian/rules clean dh clean --with python3 --buildsystem=pybuild dh_auto_clean -O--buildsystem=pybuild I: pybuild base:311: python3.13 setup.py clean /usr/lib/python3/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: MIT License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running clean removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build' (and everything under it) 'build/bdist.linux-x86_64' does not exist -- can't clean it 'build/scripts-3.13' does not exist -- can't clean it dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.13 setup.py config /usr/lib/python3/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: MIT License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3 setup.py build /usr/lib/python3/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: MIT License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running build running build_py creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel copying m2_kernel/install.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel copying m2_kernel/__main__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel copying m2_kernel/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel copying m2_kernel/kernel.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel running egg_info creating macaulay2_jupyter_kernel.egg-info writing macaulay2_jupyter_kernel.egg-info/PKG-INFO writing dependency_links to macaulay2_jupyter_kernel.egg-info/dependency_links.txt writing requirements to macaulay2_jupyter_kernel.egg-info/requires.txt writing top-level names to macaulay2_jupyter_kernel.egg-info/top_level.txt writing manifest file 'macaulay2_jupyter_kernel.egg-info/SOURCES.txt' reading manifest file 'macaulay2_jupyter_kernel.egg-info/SOURCES.txt' adding license file 'LICENSE' writing manifest file 'macaulay2_jupyter_kernel.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'm2_kernel.assets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'm2_kernel.assets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'm2_kernel.assets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'm2_kernel.assets' to be distributed and are already explicitly excluding 'm2_kernel.assets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/assets/m2-code copying m2_kernel/assets/m2-code/init.m2 -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/assets/m2-code creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/assets/m2-mode copying m2_kernel/assets/m2-mode/macaulay2.js -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/assets/m2-mode copying m2_kernel/assets/m2-mode/main.js -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/assets/m2-mode creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/assets/m2-spec copying m2_kernel/assets/m2-spec/kernel.js -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/assets/m2-spec dh_auto_test -O--buildsystem=pybuild I: pybuild base:311: cd '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build'; python3.13 -m unittest discover -v ---------------------------------------------------------------------- Ran 0 tests in 0.000s NO TESTS RAN create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild dh_auto_install --destdir=debian/macaulay2-jupyter-kernel/ -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3 setup.py install --root '/<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel' /usr/lib/python3/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: MIT License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running install /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:90: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() running build running build_py running egg_info writing macaulay2_jupyter_kernel.egg-info/PKG-INFO writing dependency_links to macaulay2_jupyter_kernel.egg-info/dependency_links.txt writing requirements to macaulay2_jupyter_kernel.egg-info/requires.txt writing top-level names to macaulay2_jupyter_kernel.egg-info/top_level.txt reading manifest file 'macaulay2_jupyter_kernel.egg-info/SOURCES.txt' adding license file 'LICENSE' writing manifest file 'macaulay2_jupyter_kernel.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'm2_kernel.assets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'm2_kernel.assets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'm2_kernel.assets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'm2_kernel.assets' to be distributed and are already explicitly excluding 'm2_kernel.assets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) running install_lib creating /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages creating /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel creating /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/__pycache__ copying /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/__pycache__/__init__.cpython-313.pyc -> /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/__pycache__ copying /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/__pycache__/kernel.cpython-313.pyc -> /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/__pycache__ creating /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/assets creating /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/assets/m2-spec copying /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/assets/m2-spec/kernel.js -> /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/assets/m2-spec creating /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/assets/m2-code copying /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/assets/m2-code/init.m2 -> /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/assets/m2-code creating /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/assets/m2-mode copying /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/assets/m2-mode/macaulay2.js -> /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/assets/m2-mode copying /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/assets/m2-mode/main.js -> /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/assets/m2-mode copying /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/install.py -> /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel copying /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/__main__.py -> /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel copying /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/__init__.py -> /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel copying /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build/m2_kernel/kernel.py -> /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel byte-compiling /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/install.py to install.cpython-313.pyc byte-compiling /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/__main__.py to __main__.cpython-313.pyc byte-compiling /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/__init__.py to __init__.cpython-313.pyc byte-compiling /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/m2_kernel/kernel.py to kernel.cpython-313.pyc running install_egg_info Copying macaulay2_jupyter_kernel.egg-info to /<<PKGBUILDDIR>>/debian/macaulay2-jupyter-kernel/usr/lib/python3.13/dist-packages/macaulay2_jupyter_kernel-0.6.7.egg-info Skipping SOURCES.txt running install_scripts debian/rules execute_after_dh_auto_install make[1]: Entering directory '/<<PKGBUILDDIR>>' cd debian && M2 --script make-macaulay2-js.m2 /usr/share/Macaulay2/Core/debugging.m2:18:13:(1):[9]: error: file not found: "/usr/share/Macaulay2/make-M2-symbols.m2" /usr/share/Macaulay2/Core/Core.m2:133:9:(1):[8]: --back trace-- /usr/share/Macaulay2/Core/Core.m2:138:29:(1):[7]: --back trace-- make-macaulay2-js.m2:1:4:(3):[6]: --back trace-- /usr/share/Macaulay2/Core/startup.m2:65:23:(0):[6]: --back trace-- /usr/share/Macaulay2/Core/Core.m2:131:28:(1):[5]: --back trace-- /usr/share/Macaulay2/Core/Core.m2:127:13:(1):[3]: --back trace-- /usr/share/Macaulay2/Core/Core.m2:138:29:(1):[2]: --back trace-- /usr/share/Macaulay2/Core/startup.m2:538:66:(0):[1]: --back trace-- /usr/share/Macaulay2/Core/startup.m2:628:30:(0): --back trace-- make[1]: *** [debian/rules:13: debian/macaulay2.js] Error 1 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:4: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --------------------------------------------------------------------------------
