[Python-modules-team] Bug#978269: pytest-openfiles: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

[Lucas Nussbaum]

Source: pytest-openfiles
Version: 0.5.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>    dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> running clean
> removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build' (and everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' 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 source format '3.0 (quilt)'
> dpkg-source: info: building pytest-openfiles using existing ./pytest-openfiles_0.5.0.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  pytest-openfiles-0.5.0/pytest_openfiles/version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/pytest-openfiles_0.5.0-1.diff.G53E1W
> dpkg-source: info: you can integrate the local changes with dpkg-source --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> --------------------------------------------------------------------------------
> Build finished at 2020-12-26T18:44:01Z

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/pytest-openfiles_0.5.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking 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 me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.