[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1046707: zope.i18nmessageid: Fails to build source after successful build



Source: zope.i18nmessageid
Version: 5.0.1-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 zope.i18nmessageid
> dpkg-buildpackage: info: source version 5.0.1-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Harlan Lieberman-Berg <hlieberman@debian.org>
>  dpkg-source --before-build .
> dpkg-source: info: using options from zope.i18nmessageid-5.0.1/debian/source/options: --extend-diff-ignore=\.egg-info
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>    dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:275: python3.11 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/dist.py:945: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated.
> !!
> 
>         ********************************************************************************
>         Please replace its usage with implicit namespaces (PEP 420).
> 
>         See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details.
>         ********************************************************************************
> 
> !!
>   ep.load()(self, ep.name, value)
> running clean
> removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_zope.i18nmessageid/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
>  dpkg-source -b .
> dpkg-source: info: using options from zope.i18nmessageid-5.0.1/debian/source/options: --extend-diff-ignore=\.egg-info
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building zope.i18nmessageid using existing ./zope.i18nmessageid_5.0.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: error: cannot represent change to src/zope/i18nmessageid/_zope_i18nmessageid_message.cpython-311-x86_64-linux-gnu.so: binary file contents changed
> dpkg-source: error: add src/zope/i18nmessageid/_zope_i18nmessageid_message.cpython-311-x86_64-linux-gnu.so in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: warning: executable mode 0755 of 'src/zope/i18nmessageid/_zope_i18nmessageid_message.cpython-311-x86_64-linux-gnu.so' will not be represented in diff
> 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/zope.i18nmessageid_5.0.1-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.


Reply to: