Source: python-django Version: 3:3.2.20-1.1 Severity: minor Tags: trixie sid ftbfs User: [email protected] Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: [email protected] 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 python-django > dpkg-buildpackage: info: source version 3:3.2.20-1.1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Gianfranco Costamagna > <[email protected]> > dpkg-source --before-build . > debian/rules clean > dh clean --with sphinxdoc,python3 --buildsystem=pybuild > debian/rules override_dh_auto_clean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > dh_auto_clean > I: pybuild base:275: python3.11 setup.py clean > /usr/lib/python3/dist-packages/setuptools/dist.py:745: > SetuptoolsDeprecationWarning: Invalid dash-separated options > !! > > > ******************************************************************************** > Usage of dash-separated 'install-script' will not be supported in > future > versions. Please use the underscore name 'install_script' instead. > > By 2023-Sep-26, you need to update your project and remove deprecated > calls > or your builds will no longer be supported. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > ******************************************************************************** > > !! > opt = self.warn_dash_deprecation(opt, section) > running clean > removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django/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 > make -C docs clean > make[2]: Entering directory '/<<PKGBUILDDIR>>/docs' > rm -rf _build/* > make[2]: Leaving directory '/<<PKGBUILDDIR>>/docs' > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_autoreconf_clean -O--buildsystem=pybuild > debian/rules override_dh_clean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > # backup~ is used in tests > dh_clean -Xbackup~ > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building python-django using existing > ./python-django_3.2.20.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > python-django-3.2.20/Django.egg-info/PKG-INFO > python-django-3.2.20/Django.egg-info/SOURCES.txt > python-django-3.2.20/Django.egg-info/entry_points.txt > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/python-django_3.2.20-1.1.diff.P3M9bT > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > 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/python-django_3.2.20-1.1_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.
