[R-pkg-team] Bug#1047300: rapache: Fails to build source after successful build

[Lucas Nussbaum]

Source: rapache
Version: 1.2.10-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 rapache
> dpkg-buildpackage: info: source version 1.2.10-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Andreas Tille <tille at debian.org>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean --with apache2
>    dh_auto_clean
> 	make -j8 distclean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> rm -rf  core mod_R.o mod_R.so *~ .libs *.o *.slo *.lo *.la .apreq-config
> rm -rf mod_R.h Makefile .depend .install libtool config.log config.status test/httpd.conf test/access_log test/error_log test/httpd.pid test/accept.lock* aclocal.m4 autom4te.cache libapreq2/library/t/Makefile libapreq2/config.nice libapreq2/module/apache/Makefile
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_autoreconf_clean
>    dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building rapache using existing ./rapache_1.2.10.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: ignoring deletion of file Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file configure, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/ltsugar.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/lt~obsolete.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/ltversion.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/libtool.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/ltoptions.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file tools/install-sh, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file tools/ltmain.sh, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file tools/missing, use --include-removal to override
> dpkg-source: info: local changes detected, the modified files are:
>  rapache-1.2.10/test/confs/load_modules
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/rapache_1.2.10-1.diff.xLHER3
> 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/rapache_1.2.10-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.