[From nobody Mon Apr 20 01:07:07 2026 Received: (at submit) by bugs.debian.org; 13 Aug 2023 21:03:34 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02 (2021-04-09) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-103.1 required=4.0 tests=ATTENDEES_DBSPAM_BODY3, ATTENDEES_DBSPAM_BODY7,BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,FROMDEVELOPER,FVGT_m_MULTI_ODD, MURPHY_DRUGS_REL8,PP_MIME_FAKE_ASCII_TEXT,SPF_HELO_NONE,SPF_NONE, UNPARSEABLE_RELAY,USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST autolearn=ham autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 23; hammy, 150; neutral, 329; spammy, 0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--pkgbuilddir, 0.000-+--PKGBUILDDIR, 0.000-+--Hx-spam-relays-external:sk:stravin, 0.000-+--H*RT:sk:stravin Return-path: <lucas@debian.org> Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:53794) from C=NA, ST=NA, L=Ankh Morpork, O=Debian SMTP, OU=Debian SMTP CA, CN=stravinsky.debian.org, EMAIL=hostmaster@stravinsky.debian.org (verified) by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.94.2) (envelope-from <lucas@debian.org>) id 1qVIFL-004DdB-L7 for submit@bugs.debian.org; Sun, 13 Aug 2023 21:03:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:Message-Id:Date:Subject:To:From: Reply-To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=ZqEcShrD8hiwczHCHBP2CeGwkW6fFe5Vzuyda4NCeiY=; b=BCttpXNmb04suPWdm2qxLig27d WyNIr9qUZUAqwqrGdmL7Hb2a1Tf20pf+58xbAsCoP6RF3Z2F9GiWuX3u0cUSGz0oF8otQ03rMr2Ik 08XWc6SmP+eXU+gS1YTpuqLujEndWMDWVxs1fH1uAJQfEulSKgTJQXXz+ximHj+IKy7CO865ArtRq YAQJeXS6qguLErfJ1Qgdu9osjVImRI76QZzpDcOmSDrcC9NFiyywp0Qc5ZbYq3Lixtm5aElo8HHde tUbMo5mHqym6xAGxTrzkWGWeJzE5vzLTYi0W95X14o314/iCC52f5mwgZ+fex+WpUR/0456mcM2FL TnHR1H3g==; Received: from authenticated user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.94.2) (envelope-from <lucas@debian.org>) id 1qVIFJ-001wIR-Lp for submit@bugs.debian.org; Sun, 13 Aug 2023 21:03:32 +0000 From: Lucas Nussbaum <lucas@debian.org> To: submit@bugs.debian.org Subject: xraylarch: Fails to build source after successful build Date: Sun, 13 Aug 2023 21:21:34 +0200 Message-Id: <1691954494.227619.1285234.nullmailer@grub.nussbaum.fr> X-Debian-User: lucas Delivered-To: submit@bugs.debian.org Source: xraylarch Version: 0.9.71+ds1-1 Severity: minor Tags: trixie sid ftbfs User: lucas@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian-qa@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 xraylarch > dpkg-buildpackage: info: source version 0.9.71+ds1-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Picca Frédéric-Emmanuel <picca@debian.org> > dpkg-source --before-build . > dpkg-source: info: using options from xraylarch-0.9.71+ds1/debian/source/options: --extend-diff-ignore=^[^/]*[.]egg-info/ > fakeroot debian/rules clean > dh clean --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/__init__.py:84: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. > !! > > ******************************************************************************** > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > ******************************************************************************** > > !! > dist.fetch_build_eggs(dist.setup_requires) > WARNING: The wheel package is not available. > running clean > removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_xraylarch/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 > #===========================================================================# > Some Python Packages were not found. Those marked with '***' are > required for larch to work, while other packages listed will mean > that some functionality will not be available: > > Package Name Version Needed for > ---------------- ---------------------------------- > tomopy 1.4 Tomographic reconstructions > wxmplot 0.9.53 Graphical User interface > ---------------- ---------------------------------- > > If you need these capabilities, you may be able to install them with > pip install <Package Name> > > or, for anaconda python, you may use > conda install -c conda-forge <Package Name> > #===========================================================================# > rm -rf .pybuild/ > find . -name \*.pyc -exec rm {} \; > rm -f debian/python3-xraylarch.debhelper.log > debian/rules execute_after_dh_auto_clean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > find . -name "*.pyc" -delete > rm -f -rf .eggs/ log*.dat > rm -f -rf xraylarch.egg-info > rm -f -rf doc/_build > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_autoreconf_clean -O--buildsystem=pybuild > dh_clean -O--buildsystem=pybuild > rm -f debian/debhelper-build-stamp > rm -rf debian/.debhelper/ > rm -f -- debian/python3-xraylarch.substvars debian/python3-xraylarch.postinst.debhelper debian/python3-xraylarch.prerm.debhelper debian/python-xraylarch-doc.substvars debian/files > rm -fr -- debian/python3-xraylarch/ debian/tmp/ debian/python-xraylarch-doc/ > 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: info: using options from xraylarch-0.9.71+ds1/debian/source/options: --extend-diff-ignore=^[^/]*[.]egg-info/ > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building xraylarch using existing ./xraylarch_0.9.71+ds1.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > xraylarch-0.9.71+ds1/doc/extensions.py > dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/xraylarch_0.9.71+ds1-1.diff.OExKyP > 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/xraylarch_0.9.71+ds1-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. ]