Your message dated Wed, 11 Mar 2026 14:34:43 +0000
with message-id <[email protected]>
and subject line Bug#1047187: fixed in xchm 2:1.38-2
has caused the Debian Bug report #1047187,
regarding xchm: Fails to build source after successful build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1047187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047187
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: xchm
Version: 2:1.35-1
Severity: minor
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: [email protected]
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 xchm
> dpkg-buildpackage: info: source version 2:1.35-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Kartik Mistry <[email protected]>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean
>    dh_auto_clean
>       make -j8 distclean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> Making distclean in m4
> make[2]: Entering directory '/<<PKGBUILDDIR>>/m4'
> 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.* xchm.po xchm.1po xchm.2po *.new.po
> rm -fr *.o
> rm -f Makefile Makefile.in POTFILES *.mo
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/po'
> Making distclean in src
> make[2]: Entering directory '/<<PKGBUILDDIR>>/src'
> test -z "xchm" || rm -f xchm
> rm -f *.o
> rm -f *.tab.c
> test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> test . = "." || test -z "" || rm -f 
> rm -f ./.deps/chm_lib.Po
> rm -f ./.deps/chmapp.Po
> rm -f ./.deps/chmfile.Po
> rm -f ./.deps/chmfinddialog.Po
> rm -f ./.deps/chmfontdialog.Po
> rm -f ./.deps/chmframe.Po
> rm -f ./.deps/chmfshandler.Po
> rm -f ./.deps/chmhtmlnotebook.Po
> rm -f ./.deps/chmhtmlwindow.Po
> rm -f ./.deps/chmindexpanel.Po
> rm -f ./.deps/chminputstream.Po
> rm -f ./.deps/chmlistctrl.Po
> rm -f ./.deps/chmsearchpanel.Po
> rm -f ./.deps/hhcparser.Po
> rm -f ./.deps/lzx.Po
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/src'
> Making distclean in art
> make[2]: Entering directory '/<<PKGBUILDDIR>>/art'
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/art'
> Making distclean in mac
> make[2]: Entering directory '/<<PKGBUILDDIR>>/mac'
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/mac'
> Making distclean in data
> make[2]: Entering directory '/<<PKGBUILDDIR>>/data'
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/data'
> Making distclean in man
> make[2]: Entering directory '/<<PKGBUILDDIR>>/man'
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/man'
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> rm -rf ./xCHM.app
> test -z "" || rm -f 
> rm -f config.h stamp-h1
> 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
> 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 xchm using existing ./xchm_1.35.orig.tar.gz
> dpkg-source: warning: ignoring deletion of file INSTALL, use 
> --include-removal to override
> dpkg-source: error: cannot represent change to po/be.gmo: binary file 
> contents changed
> dpkg-source: error: add po/be.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/bg.gmo: binary file 
> contents changed
> dpkg-source: error: add po/bg.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/cs.gmo: binary file 
> contents changed
> dpkg-source: error: add po/cs.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/el.gmo: binary file 
> contents changed
> dpkg-source: error: add po/el.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/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/hu.gmo: binary file 
> contents changed
> dpkg-source: error: add po/hu.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/it.gmo: binary file 
> contents changed
> dpkg-source: error: add po/it.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/lv.gmo: binary file 
> contents changed
> dpkg-source: error: add po/lv.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/pl.gmo: binary file 
> contents changed
> dpkg-source: error: add po/pl.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/pt_PT.gmo: binary file 
> contents changed
> dpkg-source: error: add po/pt_PT.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/ro.gmo: binary file 
> contents changed
> dpkg-source: error: add po/ro.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/ru.gmo: binary file 
> contents changed
> dpkg-source: error: add po/ru.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/sk.gmo: binary file 
> contents changed
> dpkg-source: error: add po/sk.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/sv.gmo: binary file 
> contents changed
> dpkg-source: error: add po/sv.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/xchm_1.35-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.

--- End Message ---
--- Begin Message ---
Source: xchm
Source-Version: 2:1.38-2
Done: Kartik Mistry <[email protected]>

We believe that the bug you reported is fixed in the latest version of
xchm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kartik Mistry <[email protected]> (supplier of updated xchm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 11 Mar 2026 19:41:05 +0530
Source: xchm
Architecture: source
Version: 2:1.38-2
Distribution: unstable
Urgency: low
Maintainer: Kartik Mistry <[email protected]>
Changed-By: Kartik Mistry <[email protected]>
Closes: 1047187
Changes:
 xchm (2:1.38-2) unstable; urgency=low
 .
   * debian/rules:
     + Clean stray files post build (Closes: #1047187)
Checksums-Sha1:
 e7e3c70a9b4ed83343dd34d336841d1cf6160f23 1796 xchm_1.38-2.dsc
 c4ba7ced93be5b815451c0bc628cef0b0b3529c9 6756 xchm_1.38-2.debian.tar.xz
Checksums-Sha256:
 d13f590f7d7ae4920cf6ef124e0eb62b77a3d5055bb3f7c9ceb5078b703a290f 1796 
xchm_1.38-2.dsc
 d7b4b5a24522209063f093c7eb17445347a407293f8b02b59bea7b6be2d1adb5 6756 
xchm_1.38-2.debian.tar.xz
Files:
 b2a67a0668590fa2c3a9b652566c9238 1796 x11 optional xchm_1.38-2.dsc
 8cc557febcea695c333d941963b2e79f 6756 x11 optional xchm_1.38-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAmmxeb0ACgkQAsHT8ng6
pN6T/RAArPljoZwBXNwE43r1353LMrJrpw/g/UxRNtVxul0LiStjBPQigtCiBWnn
3CpidLyd91/FQjN/q+zSCeGqpGpDOXgGXlIiAJlyYQOzepbNYbN71EvjlZL5Yxem
fiPiwLQEg1/2cUfxboGJWFGgyAddAMQS34DAqRhPQjOL/4AYiBAB+h543vhwFyr3
bdN35S88NhQPONul2Ra7j4d3g3i3c/i5UKOUhVZKm8XP/aZjreedcjYygyIqFGnU
zkXumNhE/lWSiJm5WVnQGfeFU3/ZlUb6iaWJvBdoKiGbXvOvMBFgS+gmoqQ3hNlW
qgE2MGrYLWuKNCN0HpcPmYHfAVw/P+bG2hmu05dKvC/EW6TZ5yrKl2U3l2ftlJMH
mpsyMmNYp/ngCJl9lgvK9ikC+Mstt/SYxcjr+EQeFoP9Zhi2XqkO+wWfxNCBEBP0
CBmFY/yHZJ5y/FyGIgi96bQxt6ucEjt7JmSUijs7TKxNB4P+D2JcjylJ7Z3QLs0J
Xmov4x06ssdaT5dLqT//jRnR5Bg+g5+QMI22U4LCubXERSsYyDRPpvykNz6NvmTG
qrnZVo+tQOBFFkyKCQlFQ3YVLFvUAwbIEBw3GfQAAU+/vmKf4lcxAB319Zqd/8RD
SsHhTRA68hsORMpuWf9wRxhMdygOWFIwDYODn0mEaxFhTPVJ4YY=
=hH2q
-----END PGP SIGNATURE-----

Attachment: pgpnmHaEx3UVa.pgp
Description: PGP signature


--- End Message ---

Reply via email to