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

[Lucas Nussbaum]

Source: pytest-qt
Version: 3.2.2-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):
> make[2]: Entering directory '/<<PKGBUILDDIR>>/docs'
> rm -rf _build/*
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/docs'
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_autoreconf_clean -O--buildsystem=pybuild
>    dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using options from pytest-qt-3.2.2/debian/source/options: --extend-diff-ignore=^[^/]+\.egg-info/
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building pytest-qt using existing ./pytest-qt_3.2.2.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  pytest-qt-3.2.2/pytestqt/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/pytest-qt_3.2.2-1.diff.6b26Rg
> 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:37:31Z

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/pytest-qt_3.2.2-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.