[From nobody Mon Jul 20 14:51:05 2026 Received: (at submit) by bugs.debian.org; 13 Aug 2023 13:19:02 +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,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, 62; hammy, 150; neutral, 307; 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]:35416) 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 1qVAzo-002tZs-2P for submit@bugs.debian.org; Sun, 13 Aug 2023 13:19:02 +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=Rok0O1B7KJt0su53sRUVmoud8l+zo12mK8ASMn3XdKA=; b=PrR4H4yPdacyRh6v24BqlQQ/lZ QLo8HxhVPr20kDoHWyfTiytfEGNdQyhwsQluED4dt0YCrMfhixJFxg72z1knYdMbK0dvegFVMSUOf BZhC7NhICc0cwf9tRbvM4rgY0wJIjxNRKWx6UVNq4cRJBJtWsS1BhHgQdK0smbEQ5DSPNAs5UL10v OUF0VWqAywvsHMY3pjzfDFmG3pDyLmgPK64OfS/9Z8H642NrTUIvE0KM6GxQw8p69uaNxKSUDSlEB Rx6A8BBxQiDRdzO6nl8QBH5X5hfKZxIdldaYtHBhDLKwYnJJ9zZ/wf31GHPyX2eIQ0wj91wFbPNzd z0JaRcUA==; 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 1qVAzk-001bph-O8 for submit@bugs.debian.org; Sun, 13 Aug 2023 13:19:00 +0000 From: Lucas Nussbaum <lucas@debian.org> To: submit@bugs.debian.org Subject: breezy: Fails to build source after successful build Date: Sun, 13 Aug 2023 15:17:55 +0200 Message-Id: <1691932675.873084.1210594.nullmailer@grub.nussbaum.fr> X-Debian-User: lucas Delivered-To: submit@bugs.debian.org Source: breezy Version: 3.3.3-2 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 breezy > dpkg-buildpackage: info: source version 3.3.3-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Jelmer Vernooij <jelmer@debian.org> > dpkg-source --before-build . > debian/rules clean > dh clean --with python3,sphinxdoc,bash_completion --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/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. > config = read_configuration(filepath, True, ignore_option_errors, dist) > running clean > removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_breezy/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 > running clean_rust > cargo clean --manifest-path lib-rio/Cargo.toml > cargo clean --manifest-path Cargo.toml > I: pybuild base:275: python3.11-dbg setup.py clean > /usr/lib/python3/dist-packages/setuptools_rust/build.py:22: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html > import pkg_resources > /usr/lib/python3/dist-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. > config = read_configuration(filepath, True, ignore_option_errors, dist) > /usr/lib/python3/dist-packages/babel/messages/catalog.py:13: DeprecationWarning: 'cgi' is deprecated and slated for removal in Python 3.13 > from cgi import parse_header > running clean > removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_dbg_breezy/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 > running clean_rust > cargo clean --manifest-path lib-rio/Cargo.toml > cargo clean --manifest-path Cargo.toml > rm -rf debian/brzhome > rm -f brzlib/*_pyx.c > # It also doesn't really clean every thing... > ls doc/en/user-reference/*txt | grep -v readme.txt | xargs rm -rf > rm -rf doc/developers/make.bat \ > doc/developers/Makefile \ > doc/*/_build/ \ > doc/en/release-notes/index.txt > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_autoreconf_clean -O--buildsystem=pybuild > dh_clean -O--buildsystem=pybuild > 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 breezy using existing ./breezy_3.3.3.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: file breezy-3.3.3/breezy.egg-info/SOURCES.txt has no final newline (either original or modified version) > dpkg-source: info: local changes detected, the modified files are: > breezy-3.3.3/Cargo.lock > breezy-3.3.3/breezy.egg-info/PKG-INFO > breezy-3.3.3/breezy.egg-info/SOURCES.txt > breezy-3.3.3/breezy.egg-info/dependency_links.txt > breezy-3.3.3/breezy.egg-info/not-zip-safe > breezy-3.3.3/breezy.egg-info/requires.txt > breezy-3.3.3/breezy.egg-info/top_level.txt > breezy-3.3.3/breezy/_annotator_pyx.c > breezy-3.3.3/breezy/_chunks_to_lines_pyx.c > breezy-3.3.3/breezy/_known_graph_pyx.c > breezy-3.3.3/breezy/_readdir_pyx.c > breezy-3.3.3/breezy/bzr/_btree_serializer_pyx.c > breezy-3.3.3/breezy/bzr/_chk_map_pyx.c > breezy-3.3.3/breezy/bzr/_dirstate_helpers_pyx.c > breezy-3.3.3/breezy/bzr/_groupcompress_pyx.c > breezy-3.3.3/breezy/bzr/_knit_load_data_pyx.c > breezy-3.3.3/breezy/bzr/_rio_pyx.c > breezy-3.3.3/breezy/bzr/_simple_set_pyx.c > breezy-3.3.3/breezy/bzr/_simple_set_pyx.h > breezy-3.3.3/breezy/bzr/_simple_set_pyx_api.h > breezy-3.3.3/brz.1 > dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/breezy_3.3.3-2.diff.tUlWeM > 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/breezy_3.3.3-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. ]