[Debian-astro-maintainers] Bug#1049279: pyregion: Fails to build source after successful build

Lucas Nussbaum lucas at debian.org
Sun Aug 13 20:21:09 BST 2023


Source: pyregion
Version: 2.1.1-2
Severity: minor
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian-qa at lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S
> -----------------------------------------------------------------------------------------------------------------------
> 
> dpkg-buildpackage: info: source package pyregion
> dpkg-buildpackage: info: source version 2.1.1-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Vincent Prat <vivi at debian.org>
>  dpkg-source --before-build .
>  debian/rules clean
> py3versions: no X-Python3-Version in control file, using supported versions
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>    debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> py3versions: no X-Python3-Version in control file, using supported versions
> dh_auto_clean
> I: pybuild base:275: python3.11 setup.py clean 
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:161: AstropyDeprecationWarning: The package argument to generate_version_py has been deprecated and will be removed in future. Specify the package name in setup.cfg instead
>   warnings.warn('The package argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:166: AstropyDeprecationWarning: The version argument to generate_version_py has been deprecated and will be removed in future. Specify the version number in setup.cfg instead
>   warnings.warn('The version argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:171: AstropyDeprecationWarning: The release argument to generate_version_py has been deprecated and will be removed in future. We now use the presence of the "dev" string in the version to determine whether this is a release
>   warnings.warn('The release argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/version_helpers.py:239: AstropyDeprecationWarning: The packagename argument to generate_version_py has been deprecated and will be removed in future. Specify the package name in setup.cfg instead
>   warnings.warn('The packagename argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/version_helpers.py:244: AstropyDeprecationWarning: The version argument to generate_version_py has been deprecated and will be removed in future. Specify the version number in setup.cfg instead
>   warnings.warn('The version argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/version_helpers.py:249: AstropyDeprecationWarning: The release argument to generate_version_py has been deprecated and will be removed in future. We now use the presence of the "dev" string in the version to determine whether this is a release
>   warnings.warn('The release argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:411: SetuptoolsDeprecationWarning: Deprecated API usage.
> !!
> 
>         ********************************************************************************
>         As setuptools moves its configuration towards `pyproject.toml`,
>         `setuptools.config.read_configuration` became deprecated.
> 
>         For the time being, you can use the `setuptools.config.setupcfg` module
>         to access a backward compatible API, but this module is provisional
>         and might be removed in the future.
> 
>         To read project metadata, consider using
>         ``build.util.project_wheel_metadata`` (https://pypi.org/project/build/).
>         For simple scenarios, you can also try parsing the file directly
>         with the help of ``configparser``.
>         ********************************************************************************
> 
> !!
>   conf = read_configuration(setup_cfg)
> /usr/lib/python3/dist-packages/setuptools/dist.py:945: DistDeprecationWarning: use_2to3 is ignored.
>   ep.load()(self, ep.name, value)
> running clean
> removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pyregion/build' (and everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.11' does not exist -- can't clean it
> rm -rf .cache
> rm -rf api
> rm -rf pyregion/_region_filter.c
> rm -rf pyregion.egg-info
> rm -rf build
> rm -rf .pybuild
> rm -rf .eggs
> rm -rf debian/doctrees
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_autoreconf_clean -O--buildsystem=pybuild
>    dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: error: unwanted binary file: debian/plot_directive/examples/demo_region04.hires.png
> dpkg-source: error: unwanted binary file: debian/plot_directive/examples/demo_region02.hires.png
> dpkg-source: error: unwanted binary file: debian/plot_directive/examples/demo_region02.pdf
> dpkg-source: error: unwanted binary file: debian/plot_directive/examples/demo_region01.png
> dpkg-source: error: unwanted binary file: debian/plot_directive/examples/demo_region02.png
> dpkg-source: error: unwanted binary file: debian/plot_directive/examples/demo_region01.hires.png
> dpkg-source: error: unwanted binary file: debian/plot_directive/examples/demo_region01.pdf
> dpkg-source: error: unwanted binary file: debian/plot_directive/examples/demo_region04.pdf
> dpkg-source: error: unwanted binary file: debian/plot_directive/examples/demo_region04.png
> dpkg-source: error: unwanted binary file: debian/plot_directive/figures/region_drawing.pdf
> dpkg-source: error: unwanted binary file: debian/plot_directive/figures/region_drawing2.png
> dpkg-source: error: unwanted binary file: debian/plot_directive/figures/region_drawing2.hires.png
> dpkg-source: error: unwanted binary file: debian/plot_directive/figures/region_drawing.hires.png
> dpkg-source: error: unwanted binary file: debian/plot_directive/figures/region_drawing2.pdf
> dpkg-source: error: unwanted binary file: debian/plot_directive/figures/region_drawing.png
> dpkg-source: error: detected 15 unwanted binary files (add them in debian/source/include-binaries to allow their inclusion).
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 255
> 
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/13/pyregion_2.1.1-2_unstable.log

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.



More information about the Debian-astro-maintainers mailing list