Bug#1046363: ibus-m17n: Fails to build source after successful build
Source: ibus-m17n
Version: 1.4.20-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-m17n
> dpkg-buildpackage: info: source version 1.4.20-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Gunnar Hjalmarsson <gunnarhj@debian.org>
> dpkg-source --before-build .
> debian/rules clean
> dh clean
> dh_auto_clean
> make -j8 distclean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> Making distclean in src
> make[2]: Entering directory '/<<PKGBUILDDIR>>/src'
> test -z "m17n.xml ibus-setup-m17n.desktop ibus-setup-m17n.desktop.in " || rm -f m17n.xml ibus-setup-m17n.desktop ibus-setup-m17n.desktop.in
> rm -rf .libs _libs
> rm -f test-m17n
> rm -f ibus-engine-m17n ibus-setup-m17n
> test -z "libm17ncommon.la" || rm -f libm17ncommon.la
> rm -f *.o
> test -z "test-m17n.log" || rm -f test-m17n.log
> rm -f *.lo
> rm -f *.tab.c
> test -z "" || rm -f
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> test -z "test-m17n.trs" || rm -f test-m17n.trs
> test . = "." || test -z "" || rm -f
> test -z "m17n.xml.in " || rm -f m17n.xml.in
> test -z "test-suite.log" || rm -f test-suite.log
> rm -f ./so_locations
> rm -f .deps/minput_list.Plo
> rm -f ./.deps/engine.Po
> rm -f ./.deps/ibus_setup_m17n-setup.Po
> rm -f ./.deps/m17nutil.Plo
> rm -f ./.deps/main.Po
> rm -f ./.deps/test_m17n-test.Po
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/src'
> Making distclean in icons
> make[2]: Entering directory '/<<PKGBUILDDIR>>/icons'
> make[3]: Entering directory '/<<PKGBUILDDIR>>/icons'
> rm -rf .libs _libs
> rm -f *.lo
> test -z "" || rm -f
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> test . = "." || test -z "" || rm -f
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/icons'
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/icons'
> 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-m17n.po ibus-m17n.1po ibus-m17n.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-m17n.spec" || rm -f ibus-m17n.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-m17n using existing ./ibus-m17n_1.4.20.orig.tar.gz
> dpkg-source: warning: ignoring deletion of file src/m17n.xml.in, use --include-removal to override
> dpkg-source: error: cannot represent change to po/ar.gmo: binary file contents changed
> dpkg-source: error: add po/ar.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/bn.gmo: binary file contents changed
> dpkg-source: error: add po/bn.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/de.gmo: binary file contents changed
> dpkg-source: error: add po/de.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/es.gmo: binary file contents changed
> dpkg-source: error: add po/es.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/fa.gmo: binary file contents changed
> dpkg-source: error: add po/fa.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/fr.gmo: binary file contents changed
> dpkg-source: error: add po/fr.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/id.gmo: binary file contents changed
> dpkg-source: error: add po/id.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/ja.gmo: binary file contents changed
> dpkg-source: error: add po/ja.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/ka.gmo: binary file contents changed
> dpkg-source: error: add po/ka.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/pt_BR.gmo: binary file contents changed
> dpkg-source: error: add po/pt_BR.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/si.gmo: binary file contents changed
> dpkg-source: error: add po/si.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/tr.gmo: binary file contents changed
> dpkg-source: error: add po/tr.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/uk.gmo: binary file contents changed
> dpkg-source: error: add po/uk.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/zh_CN.gmo: binary file contents changed
> dpkg-source: error: add po/zh_CN.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> 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-m17n_1.4.20-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: