Source: flask-multistatic Version: 1.0-4 Severity: minor Tags: trixie sid ftbfs User: [email protected] Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: [email protected] Usertags: qa-doublebuild
Hi, This package fails to do build a binary-only build (not source) after a successful build (dpkg-buildpackage ; dpkg-buildpackage -b). 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/DoubleBuild Relevant part of the build log: > cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -b > --------------------------------------------------------------------------------------------------------------------------------------- > > dpkg-buildpackage: info: source package flask-multistatic > dpkg-buildpackage: info: source version 1.0-4 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Debian Janitor <[email protected]> > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > fakeroot debian/rules clean > dh clean --with python3 --buildsystem=pybuild > dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:291: python3.11 setup.py clean > running clean > removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flaskext.multistatic/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 > dh_autoreconf_clean -O--buildsystem=pybuild > dh_clean -O--buildsystem=pybuild > debian/rules build > dh build --with python3 --buildsystem=pybuild > dh_update_autotools_config -O--buildsystem=pybuild > dh_autoreconf -O--buildsystem=pybuild > dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:291: python3.11 setup.py config > running config > dh_auto_build -O--buildsystem=pybuild > I: pybuild base:291: /usr/bin/python3 setup.py build > running build > running build_py > copying flask_multistatic.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flaskext.multistatic/build > dh_auto_test -O--buildsystem=pybuild > I: pybuild base:291: cd > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flaskext.multistatic/build; > python3.11 -m unittest discover -v > > ---------------------------------------------------------------------- > Ran 0 tests in 0.000s > > OK > create-stamp debian/debhelper-build-stamp > fakeroot debian/rules binary > dh binary --with python3 --buildsystem=pybuild > dh_testroot -O--buildsystem=pybuild > dh_prep -O--buildsystem=pybuild > dh_auto_install --destdir=debian/python3-flaskext.multistatic/ > -O--buildsystem=pybuild > I: pybuild base:291: /usr/bin/python3 setup.py install --root > /<<PKGBUILDDIR>>/debian/python3-flaskext.multistatic > running install > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > SetuptoolsDeprecationWarning: setup.py install is deprecated. > !! > > > ******************************************************************************** > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > for details. > > ******************************************************************************** > > !! > self.initialize_options() > running build > running build_py > running install_lib > creating /<<PKGBUILDDIR>>/debian/python3-flaskext.multistatic/usr > creating /<<PKGBUILDDIR>>/debian/python3-flaskext.multistatic/usr/lib > creating > /<<PKGBUILDDIR>>/debian/python3-flaskext.multistatic/usr/lib/python3.11 > creating > /<<PKGBUILDDIR>>/debian/python3-flaskext.multistatic/usr/lib/python3.11/dist-packages > copying > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flaskext.multistatic/build/flask_multistatic.py > -> > /<<PKGBUILDDIR>>/debian/python3-flaskext.multistatic/usr/lib/python3.11/dist-packages > byte-compiling > /<<PKGBUILDDIR>>/debian/python3-flaskext.multistatic/usr/lib/python3.11/dist-packages/flask_multistatic.py > to flask_multistatic.cpython-311.pyc > running install_egg_info > running egg_info > writing flask_multistatic.egg-info/PKG-INFO > writing dependency_links to flask_multistatic.egg-info/dependency_links.txt > writing requirements to flask_multistatic.egg-info/requires.txt > writing top-level names to flask_multistatic.egg-info/top_level.txt > reading manifest file 'flask_multistatic.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching 'example.conf' > adding license file 'LICENSE' > writing manifest file 'flask_multistatic.egg-info/SOURCES.txt' > Copying flask_multistatic.egg-info to > /<<PKGBUILDDIR>>/debian/python3-flaskext.multistatic/usr/lib/python3.11/dist-packages/flask_multistatic-1.0.egg-info > Skipping SOURCES.txt > running install_scripts > dh_installdocs -O--buildsystem=pybuild > dh_installchangelogs -O--buildsystem=pybuild > debian/rules override_dh_installexamples > make[1]: Entering directory '/<<PKGBUILDDIR>>' > mv example.conf example-httpd.conf > mv: cannot stat 'example.conf': No such file or directory > make[1]: *** [debian/rules:9: override_dh_installexamples] Error 1 > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > make: *** [debian/rules:6: binary] Error 2 > dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned > exit status 2 > > E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -b' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/16/flask-multistatic_1.0-4_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.
