| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Getting ready for the point release
|
|
|
|
|
|
|
|
The usual make message on everything being up to date is:
make: Nothing to be done for 'all'.
However, since
commit d038b9320949c79503fe4b76870aaabf279405ab
Author: David Bremner <david@tethera.net>
Date: Mon Jun 1 09:08:59 2015 +0200
build: integrate building ruby bindings into notmuch build process
if one doesn't have the ruby dependencies installed, the message has
been:
Missing dependency, skipping ruby bindings
Restore the usual behaviour by dropping the message. It's redundant
during build anyway, since the configure script already outputs:
Checking for ruby development files... No (skipping ruby bindings)
|
|
Signed-off-by: Justus Winter <justus@gnupg.org>
|
|
The notmuch python bindings document that database.remove_message
should raise an exception when the message removal fails, but they
don't actually do it.
|
|
Drop unused imports, and avoid warning about unused imports when we
import something on behalf of another module.
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
|
Remove the __len__ functions, as they exhaust the iterator, breaking
'list(x)'.
This is a follow-up to 8866a89e.
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
|
Use 'notmuch_query_search_{threads,messages}_st' instead of their
deprecated counterpart.
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
|
Add support for the new notmuch status codes UNSUPPORTED_OPERATION,
UPGRADE_REQUIRED, and PATH_ERROR.
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
|
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
|
|
|
This gives some additional access to debugging information when using
the python bindings.
Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
|
|
|
|
|
|
|
|
|
|
These changes should not be too surprising for users because the
routines were already potentially throwing exceptions.
|
|
Note that any mismatches are not detected until runtime (if at all)
with the python bindings, so tests are crucial
|
|
This change of replacing ignoring errors with exceptions is intended,
and indeed one of the main motivations for the libnotmuch API changes.
|
|
notmuch 0.20.2 release
Conflicts:
NEWS
|
|
As usual, bump python version at same time.
|
|
This is supposed to help build on systems like MacOS with different
conventions for naming shared libraries. We have already computed the
relevant names, so doing it again in ruby seems like a bad idea.
|
|
In particular this is supposed to help build on systems (presumably
using a non-gnu ld) where this flag is not available.
|
|
Because ruby generates a Makefile, we have to use recursive make.
Because mkmf.rb hardcodes the name Makefile, put our Makefile{.local}
in the parent directory.
|
|
|
|
|
|
|
|
Apparently python3 needs this.
|
|
|
|
Failing to update this string in globals.py causes failures when the
SONAME changes. In order to hopefully reduce the number of such
errors, automate the process of setting the SONAME in the python
bindings.
|
|
|
|
|
|
|
|
|
|
Sync NEWS debian/changelog at the same time, although in those cases it's a downgrade.
|
|
notmuch 0.18.2 release
|
|
No non-documentation changes
|
|
notmuch 0.18.2~rc1 release
Conflicts:
NEWS
debian/changelog
|
|
|
|
Implemented as the method `exclude_tag` of the class `Query`. This method takes
one argument, a string containing the name of the tag to exclude.
|
|
This should have happened in commit 6754ad9f9, but oops.
This was not caught by our test suite because it uses an installed
notmuch library of it cannot find the just built one.
|
|
Throw an exception if notmuch_database_destroy fails.
|
|
Add return status to the Database.Close() method that calls
notmuch_database_destroy.
|
|
Throw an exception if notmuch_database_close or notmuch_database_destroy
fail.
|
|
notmuch 0.18.1 release
|
|
Also add precis of NEWS to debian changelog
|
