From: David Bremner <david@tethera.net>
To: Jakub Wilk <jwilk@debian.org>, 683505@bugs.debian.org
Cc: notmuch@notmuchmail.org
Subject: Re: Bug#683505: notmuch: FTBFS if built twice in a row: unrepresentable changes to source
Date: Wed, 01 Aug 2012 12:14:27 -0300 [thread overview]
Message-ID: <87pq7aabl8.fsf@convex-new.cs.unb.ca> (raw)
In-Reply-To: <20120801103707.GA668@jwilk.net>
Jakub Wilk <jwilk@debian.org> writes:
> | 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
> --
> Jakub Wilk
I guess the problem here is that the notmuch build process does not
clean up the test directories in case of failing tests. I guess it
probably should if the user explicitly runs "make clean".
Any thoughts on that notmuch people? Should we add a list of test/tmp.*
to be cleaned?
d
next parent reply other threads:[~2012-08-01 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120801103707.GA668@jwilk.net>
2012-08-01 15:14 ` David Bremner [this message]
2012-08-01 15:26 ` Bug#683505: notmuch: FTBFS if built twice in a row: unrepresentable changes to source Jameson Graef Rollins
2012-08-01 21:37 ` David Bremner
2012-08-02 3:10 ` Jameson Graef Rollins
2012-08-02 10:18 ` Tomi Ollila
2012-08-02 14:33 ` Austin Clements
2012-08-02 21:12 ` Tomi Ollila
2012-08-01 16:33 ` Tomi Ollila
2012-08-02 13:22 ` Cleaning up cleaning david
2012-08-02 13:22 ` [PATCH 1/3] build system: remove directories created by tests in "make clean" david
2012-08-02 13:22 ` [PATCH 2/3] build system: remove configure output in Make distclean david
2012-08-02 13:22 ` [PATCH 3/3] debian: update changelog for cleaning changes david
2012-08-02 13:47 ` Cleaning up cleaning Tomi Ollila
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pq7aabl8.fsf@convex-new.cs.unb.ca \
--to=david@tethera.net \
--cc=683505@bugs.debian.org \
--cc=jwilk@debian.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).