Source: mat2 Version: 0.13.4-2 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@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 mat2 > dpkg-buildpackage: info: source version 0.13.4-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Georg Faerber <ge...@debian.org> > dpkg-source --before-build . > debian/rules clean > dh clean --with python3 --buildsystem=pybuild > dh_auto_clean -O--buildsystem=pybuild > pybuild --clean -i python{version} -p 3.11 > I: pybuild base:275: python3.11 setup.py clean > /usr/lib/python3/dist-packages/setuptools/config/_apply_pyprojecttoml.py:62: > _WouldIgnoreField: `description` defined outside of `pyproject.toml` would be > ignored. > !! > > > ******************************************************************************** > > ########################################################################## > # configuration would be ignored/result in error due to > `pyproject.toml` # > > ########################################################################## > > The following seems to be defined outside of `pyproject.toml`: > > `description = 'A handy tool to trash your metadata'` > > According to the spec (see the link below), however, setuptools CANNOT > consider this value unless `description` is listed as `dynamic`. > > > https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ > > For the time being, `setuptools` will still consider the given value > (as a > **transitional** measure), but please note that future releases of > setuptools will > follow strictly the standard. > > To prevent this warning, you can list `description` under `dynamic` > or alternatively > remove the `[project]` table from your file and rely entirely on > other means of > configuration. > > By 2023-Oct-30, you need to update your project and remove deprecated > calls > or your builds will no longer be supported. > > ******************************************************************************** > > !! > _handle_missing_dynamic(dist, project_table) > /usr/lib/python3/dist-packages/setuptools/config/_apply_pyprojecttoml.py:62: > _WouldIgnoreField: `authors` defined outside of `pyproject.toml` would be > ignored. > !! > > > ******************************************************************************** > > ########################################################################## > # configuration would be ignored/result in error due to > `pyproject.toml` # > > ########################################################################## > > The following seems to be defined outside of `pyproject.toml`: > > `authors = 'Julien (jvoisin) Voisin'` > > According to the spec (see the link below), however, setuptools CANNOT > consider this value unless `authors` is listed as `dynamic`. > > > https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ > > For the time being, `setuptools` will still consider the given value > (as a > **transitional** measure), but please note that future releases of > setuptools will > follow strictly the standard. > > To prevent this warning, you can list `authors` under `dynamic` or > alternatively > remove the `[project]` table from your file and rely entirely on > other means of > configuration. > > By 2023-Oct-30, you need to update your project and remove deprecated > calls > or your builds will no longer be supported. > > ******************************************************************************** > > !! > _handle_missing_dynamic(dist, project_table) > /usr/lib/python3/dist-packages/setuptools/config/_apply_pyprojecttoml.py:62: > _WouldIgnoreField: `classifiers` defined outside of `pyproject.toml` would be > ignored. > !! > > > ******************************************************************************** > > ########################################################################## > # configuration would be ignored/result in error due to > `pyproject.toml` # > > ########################################################################## > > The following seems to be defined outside of `pyproject.toml`: > > `classifiers = ['Development Status :: 3 - Alpha', 'Environment :: > Console', 'License :: OSI Approved :: GNU Lesser General Public License v3 or > later (LGPLv3+)', 'Operating System :: OS Independent', 'Programming Language > :: Python :: 3 :: Only', 'Topic :: Security', 'Intended Audience :: End > Users/Desktop']` > > According to the spec (see the link below), however, setuptools CANNOT > consider this value unless `classifiers` is listed as `dynamic`. > > > https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ > > For the time being, `setuptools` will still consider the given value > (as a > **transitional** measure), but please note that future releases of > setuptools will > follow strictly the standard. > > To prevent this warning, you can list `classifiers` under `dynamic` > or alternatively > remove the `[project]` table from your file and rely entirely on > other means of > configuration. > > By 2023-Oct-30, you need to update your project and remove deprecated > calls > or your builds will no longer be supported. > > ******************************************************************************** > > !! > _handle_missing_dynamic(dist, project_table) > /usr/lib/python3/dist-packages/setuptools/config/_apply_pyprojecttoml.py:62: > _WouldIgnoreField: `urls` defined outside of `pyproject.toml` would be > ignored. > !! > > > ******************************************************************************** > > ########################################################################## > # configuration would be ignored/result in error due to > `pyproject.toml` # > > ########################################################################## > > The following seems to be defined outside of `pyproject.toml`: > > `urls = {'bugtacker': 'https://0xacab.org/jvoisin/mat2/issues'}` > > According to the spec (see the link below), however, setuptools CANNOT > consider this value unless `urls` is listed as `dynamic`. > > > https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ > > For the time being, `setuptools` will still consider the given value > (as a > **transitional** measure), but please note that future releases of > setuptools will > follow strictly the standard. > > To prevent this warning, you can list `urls` under `dynamic` or > alternatively > remove the `[project]` table from your file and rely entirely on > other means of > configuration. > > By 2023-Oct-30, you need to update your project and remove deprecated > calls > or your builds will no longer be supported. > > ******************************************************************************** > > !! > _handle_missing_dynamic(dist, project_table) > /usr/lib/python3/dist-packages/setuptools/config/_apply_pyprojecttoml.py:62: > _WouldIgnoreField: `dependencies` defined outside of `pyproject.toml` would > be ignored. > !! > > > ******************************************************************************** > > ########################################################################## > # configuration would be ignored/result in error due to > `pyproject.toml` # > > ########################################################################## > > The following seems to be defined outside of `pyproject.toml`: > > `dependencies = ['mutagen', 'PyGObject', 'pycairo']` > > According to the spec (see the link below), however, setuptools CANNOT > consider this value unless `dependencies` is listed as `dynamic`. > > > https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ > > For the time being, `setuptools` will still consider the given value > (as a > **transitional** measure), but please note that future releases of > setuptools will > follow strictly the standard. > > To prevent this warning, you can list `dependencies` under `dynamic` > or alternatively > remove the `[project]` table from your file and rely entirely on > other means of > configuration. > > By 2023-Oct-30, you need to update your project and remove deprecated > calls > or your builds will no longer be supported. > > ******************************************************************************** > > !! > _handle_missing_dynamic(dist, project_table) > running clean > removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/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 .pybuild/ > find . -name \*.pyc -exec rm {} \; > dh_autoreconf_clean -O--buildsystem=pybuild > dh_clean -O--buildsystem=pybuild > rm -f debian/debhelper-build-stamp > rm -rf debian/.debhelper/ > rm -f -- debian/mat2.substvars debian/mat2.postinst.debhelper > debian/mat2.prerm.debhelper debian/files > rm -fr -- debian/mat2/ debian/tmp/ > find . \( \( \ > \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path > .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o > -type f -a \ > \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \ > -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \ > -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \ > -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \ > \) -exec rm -f {} + \) -o \ > \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) > \) > dpkg-source -b . > dpkg-source: warning: upstream signing key but no upstream tarball signature > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building mat2 using existing ./mat2_0.13.4.orig.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: file mat2-0.13.4/mat.egg-info/SOURCES.txt has no final > newline (either original or modified version) > dpkg-source: error: cannot represent change to tests/data/clean.cleaned.docx: > binary file contents changed > dpkg-source: error: add tests/data/clean.cleaned.docx in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to tests/data/clean.cleaned.zip: > binary file contents changed > dpkg-source: error: add tests/data/clean.cleaned.zip in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: unrepresentable changes to source > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 1 > > 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/mat2_0.13.4-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.
