Bug#1046785: ibus-array: Fails to build source after successful build
Source: ibus-array
Version: 0.2.2-1
Severity: minor
Tags: trixie sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian-qa@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 ibus-array
> dpkg-buildpackage: info: source version 0.2.2-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Boyuan Yang <byang@debian.org>
> dpkg-source --before-build .
> debian/rules clean
> dh clean --with python3,autoreconf
> dh_auto_clean
> make -j8 distclean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> Making distclean in src
> make[2]: Entering directory '/<<PKGBUILDDIR>>/src'
> test -z "array.xml " || rm -f array.xml
> rm -rf .libs _libs
> rm -f *.o
> rm -f *.lo
> rm -f *.tab.c
> test -z "array.inputMethod.xml.in" || rm -f array.inputMethod.xml.in
> rm -f ibus-engine-array
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> test . = "." || test -z "" || rm -f
> rm -f ./.deps/ibus_engine_array-array.Po
> rm -f ./.deps/ibus_engine_array-engine.Po
> rm -f ./.deps/ibus_engine_array-main.Po
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/src'
> Making distclean in setup
> make[2]: Entering directory '/<<PKGBUILDDIR>>/setup'
> test -z "*.pyc " || rm -f *.pyc
> rm -rf .libs _libs
> rm -f *.lo
> test -z "ibus-setup-array config.py" || rm -f ibus-setup-array config.py
> test . = "." || test -z "" || rm -f
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/setup'
> Making distclean in icons
> make[2]: Entering directory '/<<PKGBUILDDIR>>/icons'
> rm -rf .libs _libs
> rm -f *.lo
> test -z "" || rm -f
> test . = "." || test -z "" || rm -f
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/icons'
> Making distclean in data
> make[2]: Entering directory '/<<PKGBUILDDIR>>/data'
> rm -rf .libs _libs
> rm -f *.lo
> test -z "" || rm -f
> test . = "." || test -z "" || rm -f
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/data'
> Making distclean in m4
> make[2]: Entering directory '/<<PKGBUILDDIR>>/m4'
> rm -rf .libs _libs
> rm -f *.lo
> test -z "" || rm -f
> test . = "." || test -z "" || rm -f
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/m4'
> Making distclean in po
> make[2]: Entering directory '/<<PKGBUILDDIR>>/po'
> rm -f *.insert-header
> rm -f remove-potcdate.sed
> rm -f stamp-poT
> rm -f core core.* ibus-array.po ibus-array.1po ibus-array.2po *.new.po
> rm -fr *.o
> rm -f Makefile Makefile.in POTFILES *.mo
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/po'
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> rm -rf .libs _libs
> rm -f -r "`uname -i`"
> rm -f *.lo
> test -z "ibus-array.spec" || rm -f ibus-array.spec
> rm -f config.h stamp-h1
> rm -f libtool config.lt
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> test . = "." || test -z "" || rm -f
> rm -f cscope.out cscope.in.out cscope.po.out cscope.files
> test -z "po/stamp-it " || rm -f po/stamp-it
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> 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 ibus-array using existing ./ibus-array_0.2.2.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: ignoring deletion of file install-sh, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file INSTALL, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file compile, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file depcomp, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file missing, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/ltsugar.m4, use --include-removal to override
> dpkg-source: error: cannot represent change to po/zh_TW.gmo: binary file contents changed
> dpkg-source: error: add po/zh_TW.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: unrepresentable changes to source
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 1
>
> 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/ibus-array_0.2.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.
Reply to: