Bug#1046487: librime: Fails to build source after successful build
Source: librime
Version: 1.8.5+dfsg1-2
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 librime
> dpkg-buildpackage: info: source version 1.8.5+dfsg1-2
> 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 --buildsystem=cmake
> dh_auto_clean -O--buildsystem=cmake
> dh_autoreconf_clean -O--buildsystem=cmake
> dh_clean -O--buildsystem=cmake
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building librime using existing ./librime_1.8.5+dfsg1.orig-librime-charcode.tar.xz
> dpkg-source: info: building librime using existing ./librime_1.8.5+dfsg1.orig-librime-lua.tar.xz
> dpkg-source: info: building librime using existing ./librime_1.8.5+dfsg1.orig-librime-octagram.tar.xz
> dpkg-source: info: building librime using existing ./librime_1.8.5+dfsg1.orig.tar.xz
> dpkg-source: info: local changes detected, the modified files are:
> librime-1.8.5+dfsg1/plugins/charcode/CMakeLists.txt
> librime-1.8.5+dfsg1/plugins/charcode/action-install.sh
> librime-1.8.5+dfsg1/plugins/charcode/src/charcode_module.cc
> librime-1.8.5+dfsg1/plugins/charcode/src/codepoint_translator.cc
> librime-1.8.5+dfsg1/plugins/charcode/src/codepoint_translator.h
> librime-1.8.5+dfsg1/plugins/charcode/src/extended_charset_filter.cc
> librime-1.8.5+dfsg1/plugins/charcode/src/extended_charset_filter.h
> librime-1.8.5+dfsg1/plugins/charcode/test/CMakeLists.txt
> librime-1.8.5+dfsg1/plugins/charcode/test/charcode_test_main.cc
> librime-1.8.5+dfsg1/plugins/charcode/test/extended_charset_filter_test.cc
> librime-1.8.5+dfsg1/plugins/octagram/CMakeLists.txt
> librime-1.8.5+dfsg1/plugins/octagram/LICENSE
> librime-1.8.5+dfsg1/plugins/octagram/src/gram_db.cc
> librime-1.8.5+dfsg1/plugins/octagram/src/gram_db.h
> librime-1.8.5+dfsg1/plugins/octagram/src/gram_encoding.cc
> librime-1.8.5+dfsg1/plugins/octagram/src/gram_encoding.h
> librime-1.8.5+dfsg1/plugins/octagram/src/grammar_module.cc
> librime-1.8.5+dfsg1/plugins/octagram/src/octagram.cc
> librime-1.8.5+dfsg1/plugins/octagram/src/octagram.h
> librime-1.8.5+dfsg1/plugins/octagram/tools/CMakeLists.txt
> librime-1.8.5+dfsg1/plugins/octagram/tools/build_grammar.cc
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/librime_1.8.5+dfsg1-2.diff.oE5MHH
> 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/librime_1.8.5+dfsg1-2_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: