[Debian-astro-maintainers] Bug#1057543: astroquery: FTBFS: ModuleNotFoundError: No module named 'imp'

[Santiago Vila]

Package: src:astroquery
Version: 0.4.6+dfsg-4
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
dh_auto_clean
I: pybuild base:310: python3.12 setup.py clean
Traceback (most recent call last):
   File "/<<PKGBUILDDIR>>/setup.py", line 16, in <module>
     from astropy_helpers.setup_helpers import setup
   File "/usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py", line 27, in <module>
     from .distutils_helpers import (add_command_option, get_compiler_option,
   File "/usr/lib/python3/dist-packages/astropy_helpers/distutils_helpers.py", line 18, in <module>
     from .utils import silence
   File "/usr/lib/python3/dist-packages/astropy_helpers/utils.py", line 4, in <module>
     import imp
ModuleNotFoundError: No module named 'imp'
E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: python3.12 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11" returned exit code 13
make[1]: *** [debian/rules:33: override_dh_auto_clean] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:13: clean] Error 2
dpkg-buildpackage: error: debian/rules clean 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/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using 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.