Package: cfv Version: 1.18-2 Severity: serious Tags: patch Hi,
building the package cfv in a clean sid build environment (with pbuilder) on i386 results in: ========================================================================= [...] dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; using uid of process (65534) dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; using uid of process (65534) dpkg-buildpackage: host architecture i386 dpkg-checkbuilddeps: warning: no utmp entry available and LOGNAME not defined; using uid of process (65534) dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; using uid of process (65534) dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; using uid of process (65534) fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp # Add here commands to clean up after the build process. /usr/bin/make PYTHON=python2.3 clean make[1]: Entering directory `/tmp/buildd/cfv-1.18' rm *.py[co] cfv.wrapper rm: cannot remove `*.py[co]': No such file or directory rm: cannot remove `cfv.wrapper': No such file or directory make[1]: [clean] Error 1 (ignored) make[1]: Leaving directory `/tmp/buildd/cfv-1.18' dh_clean dh_clean: Compatibility levels before 4 are deprecated. dpkg-source -b cfv-1.18 dpkg-source: warning: no utmp entry available and LOGNAME not defined; using uid of process (65534) dpkg-parsechangelog: warning: no utmp entry available and LOGNAME not defined; using uid of process (65534) debian: warning: no utmp entry available and LOGNAME not defined; using uid of process (65534) dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; using uid of process (65534) dpkg-source: building cfv using existing cfv_1.18.orig.tar.gz dpkg-source: building cfv in cfv_1.18-2.diff.gz dpkg-source: cannot represent change to test/test.log: binary file contents changed dpkg-source: building cfv in cfv_1.18-2.dsc dpkg-source: unrepresentable changes to source ========================================================================= Just removing test/test.log from the diff helps. Thanks for considering. -- DARTS - Debian Archive Regression Test Suite http://darts.alioth.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]