Your message dated Fri, 1 Nov 2024 12:39:13 +0100
with message-id <f6cd227b-54b8-4220-b6af-d216d2aba...@debian.org>
and subject line ndcube: FTBFS: ModuleNotFoundError: No module named
'sunpy_sphinx_theme.conf'
has caused the Debian Bug report #1086365,
regarding ndcube: FTBFS: ModuleNotFoundError: No module named
'sunpy_sphinx_theme.conf'
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 ow...@bugs.debian.org
immediately.)
--
1086365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ndcube
Version: 2.2.2-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
--------------------------------------------------------------------------------
[...]
debian/rules binary
dh binary --with python3,sphinxdoc --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.12 setup.py config
WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml
does not contain a tool.setuptools_scm section'
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/setuptools_scm/_integration/pyproject_reading.py",
line 36, in read_pyproject
section = defn.get("tool", {})[tool_name]
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
KeyError: 'setuptools_scm'
running config
debian/rules override_dh_auto_build
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_build
I: pybuild base:311: /usr/bin/python3 setup.py build
WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml
does not contain a tool.setuptools_scm section'
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/setuptools_scm/_integration/pyproject_reading.py",
line 36, in read_pyproject
section = defn.get("tool", {})[tool_name]
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
KeyError: 'setuptools_scm'
running build
running build_py
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube
copying ndcube/ndcube_sequence.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube
copying ndcube/conftest.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube
copying ndcube/_version.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube
copying ndcube/version.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube
copying ndcube/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube
copying ndcube/ndcube.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube
copying ndcube/global_coords.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube
copying ndcube/ndcollection.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/extra_coords
copying ndcube/extra_coords/table_coord.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/extra_coords
copying ndcube/extra_coords/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/extra_coords
copying ndcube/extra_coords/extra_coords.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/extra_coords
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/mixins
copying ndcube/mixins/ndslicing.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/mixins
copying ndcube/mixins/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/mixins
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/visualization
copying ndcube/visualization/descriptor.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/visualization
copying ndcube/visualization/mpl_plotter.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/visualization
copying ndcube/visualization/base.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/visualization
copying ndcube/visualization/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/visualization
copying ndcube/visualization/mpl_sequence_plotter.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/visualization
copying ndcube/visualization/plotting_utils.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/visualization
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils
copying ndcube/utils/collection.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils
copying ndcube/utils/wcs.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils
copying ndcube/utils/cube.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils
copying ndcube/utils/wcs_high_level_conversion.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils
copying ndcube/utils/misc.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils
copying ndcube/utils/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils
copying ndcube/utils/sequence.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs
copying ndcube/wcs/tools.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs
copying ndcube/wcs/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/tests
copying ndcube/tests/test_ndcube.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/tests
copying ndcube/tests/test_global_coords.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/tests
copying ndcube/tests/test_ndcollection.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/tests
copying ndcube/tests/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/tests
copying ndcube/tests/test_ndcubesequence.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/tests
copying ndcube/tests/helpers.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/tests
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils/tests
copying ndcube/utils/tests/test_utils_collection.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils/tests
copying ndcube/utils/tests/test_utils_wcs.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils/tests
copying ndcube/utils/tests/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils/tests
copying ndcube/utils/tests/test_utils_cube.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils/tests
copying ndcube/utils/tests/test_utils_sequence.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils/tests
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/wrappers
copying ndcube/wcs/wrappers/reordered_wcs.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/wrappers
copying ndcube/wcs/wrappers/compound_wcs.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/wrappers
copying ndcube/wcs/wrappers/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/wrappers
copying ndcube/wcs/wrappers/resampled_wcs.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/wrappers
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/wrappers/tests
copying ndcube/wcs/wrappers/tests/conftest.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/wrappers/tests
copying ndcube/wcs/wrappers/tests/test_reordered_wcs.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/wrappers/tests
copying ndcube/wcs/wrappers/tests/test_compound_wcs.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/wrappers/tests
copying ndcube/wcs/wrappers/tests/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/wrappers/tests
copying ndcube/wcs/wrappers/tests/test_resampled_wcs.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/wrappers/tests
running egg_info
writing ndcube.egg-info/PKG-INFO
writing dependency_links to ndcube.egg-info/dependency_links.txt
writing requirements to ndcube.egg-info/requires.txt
writing top-level names to ndcube.egg-info/top_level.txt
reading manifest file 'ndcube.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files found matching '.codecov.yaml'
warning: no previously-included files found matching '.mailmap'
warning: no previously-included files found matching '.gitignore'
warning: no previously-included files found matching '.pre-commit-config.yaml'
warning: no previously-included files found matching '.readthedocs.yml'
no previously-included directories found matching '.circleci'
no previously-included directories found matching '.github'
no previously-included directories found matching 'changelog'
no previously-included directories found matching 'ndcube/_dev'
adding license file 'LICENSE.rst'
writing manifest file 'ndcube.egg-info/SOURCES.txt'
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ndcube.extra_coords.tests' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ndcube.extra_coords.tests' 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 'ndcube.extra_coords.tests' 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 'ndcube.extra_coords.tests' to be distributed and are
already explicitly excluding 'ndcube.extra_coords.tests' 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)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ndcube.utils.sphinx' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ndcube.utils.sphinx' 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 'ndcube.utils.sphinx' 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 'ndcube.utils.sphinx' to be distributed and are
already explicitly excluding 'ndcube.utils.sphinx' 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)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ndcube.visualization.tests' is absent from the `packages`
configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ndcube.visualization.tests' 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 'ndcube.visualization.tests' 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 'ndcube.visualization.tests' to be distributed and are
already explicitly excluding 'ndcube.visualization.tests' 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)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ndcube.wcs.tests' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ndcube.wcs.tests' 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 'ndcube.wcs.tests' 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 'ndcube.wcs.tests' to be distributed and are
already explicitly excluding 'ndcube.wcs.tests' 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.12_ndcube/build/ndcube/extra_coords/tests
copying ndcube/extra_coords/tests/test_extra_coords.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/extra_coords/tests
copying ndcube/extra_coords/tests/test_lookup_table_coord.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/extra_coords/tests
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/visualization/tests
copying ndcube/visualization/tests/figure_hashes_mpl_372_ft_261_astropy_533_animators_100.json
->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/visualization/tests
copying ndcube/visualization/tests/figure_hashes_mpl_dev_ft_261_astropy_dev_animators_dev.json
->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/visualization/tests
copying ndcube/visualization/tests/test_plotting.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/visualization/tests
copying ndcube/visualization/tests/test_plotting_utils.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/visualization/tests
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils/sphinx
copying ndcube/utils/sphinx/code_context.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/utils/sphinx
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/tests
copying ndcube/wcs/tests/test_tools.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_ndcube/build/ndcube/wcs/tests
PYTHONPATH=. sphinx-build -D html_last_updated_fmt="September 13, 2024" -D
html_show_copyright=0 -N -bhtml docs/ build/html # HTML generator
Running Sphinx v7.4.7
Configuration error:
There is a programmable error in your configuration file:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sphinx/config.py", line 529, in
eval_config_file
exec(code, namespace) # NoQA: S102
^^^^^^^^^^^^^^^^^^^^^
File "/<<PKGBUILDDIR>>/docs/conf.py", line 95, in <module>
from sunpy_sphinx_theme.conf import * # NOQA
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'sunpy_sphinx_theme.conf'
make[1]: *** [debian/rules:18: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:14: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202410/
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 affects, so that this is still visible in the BTS web
page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: ndcube
Source-Version: 2.2.4-1
Done: Ole Streicher <oleb...@debian.org>
This is fixed by upstream in 2.2.4 and just not mentioned in the
changelog of 2.2.4-1.
Best
Ole
--- End Message ---
