* David Bremner <da...@tethera.net>, 2012-08-01, 12:14:
| dpkg-source: error: cannot represent change to
test/tmp.json/mail/.notmuch/xapian/record.baseB: binary file contents changed
| dpkg-source: error: add test/tmp.json/mail/.notmuch/xapian/record.baseB in
debian/source/include-binaries if you want to store the modified binary in the
debian tarball
I guess the problem here is that the notmuch build process does not
clean up the test directories in case of failing tests.
Ah, you are right, tests failed here (likely because of craziness of my
build env., not a notmuch bug), which I didn't notice as the build
succeeded. However, even if they do succeed, the second build fails
with:
| dpkg-source -b notmuch-0.13.2
| dpkg-source: info: using source format `3.0 (quilt)'
| dpkg-source: info: building notmuch using existing
./notmuch_0.13.2.orig.tar.gz
| dpkg-source: info: local changes detected, the modified files are:
| notmuch-0.13.2/.first-build-message
| notmuch-0.13.2/Makefile.config
| dpkg-source: info: you can integrate the local changes with dpkg-source
--commit
| dpkg-source: error: aborting due to unexpected upstream changes, see
/tmp/notmuch_0.13.2-1.diff.K6ZVIS
| dpkg-buildpackage: error: dpkg-source -b notmuch-0.13.2 gave error exit
status 2
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
