Bug#1043690: apertium-eo-es: Fails to build source after successful build

[Lucas Nussbaum]

Source: apertium-eo-es
Version: 1:0.9.2-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 apertium-eo-es
> dpkg-buildpackage: info: source version 1:0.9.2-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Kartik Mistry <kartik at debian.org>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean
>    dh_auto_clean
> 	make -j8 distclean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> test -z "-rf es-eo.automorf.bin es-eo.autobil.bin es-eo.autogen.bin es-eo.autopgen.bin es-eo.t1x.bin es-eo.antaux1_t2x.bin es-eo.antaux2_t2x.bin es-eo.antaux3_t2x.bin es-eo.antaux4_t2x.bin es-eo.antaux5_t2x.bin es-eo.t2x.bin es-eo.t3x.bin es-eo.rlx.bin modes es-eo.mode es-eo-no_cg.mode modes " || rm -f -rf es-eo.automorf.bin es-eo.autobil.bin es-eo.autogen.bin es-eo.autopgen.bin es-eo.t1x.bin es-eo.antaux1_t2x.bin es-eo.antaux2_t2x.bin es-eo.antaux3_t2x.bin es-eo.antaux4_t2x.bin es-eo.antaux5_t2x.bin es-eo.t2x.bin es-eo.t3x.bin es-eo.rlx.bin modes es-eo.mode es-eo-no_cg.mode modes 
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f config.status config.cache config.log configure.lineno config.status.lineno
> rm -f 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 apertium-eo-es using existing ./apertium-eo-es_0.9.2.orig.tar.bz2
> dpkg-source: info: local changes detected, the modified files are:
>  apertium-eo-es-0.9.2/ap_include.am
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/apertium-eo-es_0.9.2-1.diff.oYOeKE
> 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/apertium-eo-es_0.9.2-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.