[Debian-pan-maintainers] Bug#1046617: xrayutilities: Fails to build source after successful build

[Lucas Nussbaum]

Source: xrayutilities
Version: 1.7.4-1
Severity: minor
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian-qa at 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 xrayutilities
> dpkg-buildpackage: info: source version 1.7.4-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Picca Frédéric-Emmanuel <picca at debian.org>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean --buildsystem=pybuild
>    dh_auto_clean -O--buildsystem=pybuild
> 	pybuild --clean -i python{version} -p 3.11
> 	rm -rf .pybuild/
> 	find . -name \*.pyc -exec rm {} \;
>    dh_autoreconf_clean -O--buildsystem=pybuild
>    dh_clean -O--buildsystem=pybuild
> 	rm -f debian/debhelper-build-stamp
> 	rm -rf debian/.debhelper/
> 	rm -f debian/python-xrayutilities-doc.debhelper.log debian/python3-xrayutilities.debhelper.log debian/xrayutilities.debhelper.log
> 	rm -f -- debian/xrayutilities.substvars debian/python3-xrayutilities.substvars debian/python3-xrayutilities.postinst.debhelper debian/python3-xrayutilities.prerm.debhelper debian/python-xrayutilities-doc.substvars debian/files
> 	rm -fr -- debian/xrayutilities/ debian/tmp/ debian/python3-xrayutilities/ debian/python-xrayutilities-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 source format '3.0 (quilt)'
> dpkg-source: info: building xrayutilities using existing ./xrayutilities_1.7.4.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  xrayutilities-1.7.4/lib/xrayutilities.egg-info/PKG-INFO
>  xrayutilities-1.7.4/lib/xrayutilities.egg-info/SOURCES.txt
>  xrayutilities-1.7.4/lib/xrayutilities.egg-info/requires.txt
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/xrayutilities_1.7.4-1.diff.wEZHbY
> 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/xrayutilities_1.7.4-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.