| Commit message (Collapse) | Author | Age |
|---|
| |\
| |
| |
| |
| |
| | |
Conflicts:
notmuch-reply.c
notmuch.1
|
| | | |
|
| | |
| |
| |
| | |
as usual for pre-releases, fairly minimal commentary.
|
| | |
| |
| |
| | |
Set dist=experimental the first time.
|
| | |
| |
| |
| | |
Previous version was actually uploaded to experimental, not unstable
|
| | |
| |
| |
| | |
and keep python, man page, and debian package in sync.
|
| |/
|
|
|
| |
We now have man pages in sections 5 and 7 as well, so we copy the
whole /usr/share/man hierarchy.
|
| |
|
|
| |
Debian tags have been using '/', instead of '-' as a separator.
|
| |\
| |
| |
| |
| |
| |
| | |
Conflicts:
NEWS
Conflicts resolved by inserting the 0.10.2 stanza before 0.11
|
| | | |
|
| | | |
|
| |\| |
|
| | | |
|
| |/
|
|
|
|
| |
Since version 0.8 of dtach -n does no longer require controlling
tty to be present when executed. Currently controlling tty is not
always (if ever) present when tests are executed.
|
| |
|
|
| |
Give a brief summary of (and pointer to) NEWS
|
| |
|
|
|
| |
Arguably editing debian/changelog violates the "do one thing at a
time" rule, but all of these versions need to be kept in sync.
|
| |
|
|
| |
Since this is only an added symbol, no soname bump required.
|
| |
|
|
|
| |
The changelog is a bit minimalist, but we'll do better for the real
release.
|
| |
|
|
|
| |
This reflects a modification to the test suite to use dtach instead of
screen.
|
| |
|
|
|
| |
No functional change, but this will make for cleaner diffs down the
line.
|
| |
|
|
| |
This is needed for emacs tests, now that those are run in screen.
|
| |
|
|
|
| |
Admit that there have been no changes since the last release
candidate.
|
| |
|
|
| |
Document upstream changes since 0.9~rc1-1
|
| |
|
|
|
|
|
|
| |
we need
- a new changelog stanza, because the symbols files need a new version
- s/libnotmuch1/libnotmuch2/ everywhere
- update symbols file, s/.so.1/.so.2/, and bump minimum versions on changed
symbols (although the latter is just documentation)
|
| | |
|
| |
|
|
| |
This is needed to enable the atomicity tests at build time.
|
| |
|
|
|
| |
The bug was really closed by the commit that updated the dependency,
of course.
|
| |
|
|
|
|
| |
As long as we have no version information in the json output, this
seems like the only possible way of ensuring that the emacs client
code understands the output from the command line tool notmuch.
|
| | |
|
| |
|
|
|
| |
There are three new symbols in libnotmuch. In addition to notmuch_{begin,end)_atomic,
notmuch_database_find_message_by_filename was exposed.
|
| | |
|
| |
|
|
| |
See commit 6979b65 for more discussion.
|
| |
|
|
|
|
|
|
|
|
| |
we now have three files to keep in sync. That seems wrong, but I guess
we will live with it for now.
The main problem is that the python code is distributed separately, so
it can't get the version from 'version'.
The choice ~rcX is for convenience with debian versioning.
|
| |
|
|
|
| |
No actual changes, but we need a new stanza to upload to unstable
anyway.
|
| |
|
|
|
|
|
|
| |
This reverts commit 2b76283b52a2389a591ca055b086381c44e2a61f.
Conflicts:
debian/rules
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This generates a seperate notmuch-0.x.debian.tar.gz containing
./debian.
In the initial release this is redundant, but for Debian only updates
between releases, this allows updating the contents of ./debian, and
using the rest of the release tarball.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
There is concensus to use non-native version number for updates that
contain only Debian changes. Unfortunately changing back and forth
between native and non-native packages has the potential for
confusion, since the archive will end up with notmuch-0.x.tar.gz and
notmuch-0.x.orig.tar.gz. So we use non-native numbering from the
beginning.
|
| |
|
|
|
| |
These are exported (again) by the library to prevent problems with
catching exceptions.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It took quite some time to debug why folder: searches didn't work for me
though I had notmuch 0.6~rc1 installed. amdragon in #notmuch found out
that I still had libnotmuch1 0.5+nmu3 installed.
To prevent the same problem in the future let notmuch depend on the same
version of libnotmuch1.
Reviewed-By: David Bremner <david@tethera.net>
The underlying issue is that the libnotmuch interface is not
entirely captured by the set of exported symbols. In particular the
query syntax can change without being visible to the linker at all.
|
| |
|
|
|
|
| |
The version numbering scheme of n.n.n is chosen so as not to confuse
tools that rely on the presence of a dash to detect non-native
packages.
|
| |
|
|
|
| |
The notmuch-vim README.Debian in particular is quite important since
it discussions the need to install the package with vim-addons
|
| |
|
|
|
| |
This perhaps breaks the "one thing at a time rule", but seems better
than leaving the changelog pointing to nothing.
|
| |
|
|
|
|
|
|
|
| |
This step was missed during the package split of notmuch to notmuch,
notmuch-emacs, and notmuch-vim.
It seems mostly harmless in this case, but it is silly for non-vim
users to have those directories.
(cherry picked from commit 4b5875d81ef80dd7138e178f59ac67f66d5fe0ab)
|
| |
|
|
|
|
|
| |
The last upload to experimental was really a release candidate too.
Switch versioning to ~rc1 as counting commits is confusing when
building from the release branch.
(cherry picked from commit 117852a5f1269e77a7f76c53236220a9ec89eba6)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
as of version 4.3.12, perhaps earlier, the Debian zsh package now
ships /usr/share/zsh/functions/Completion/Unix/_notmuch, so we
shouldn't install that ourselves anymore.
My understanding is that letting zsh ship the completion scripts is
the standard thing to do.
The script is still shipped in /usr/share/doc/notmuch/examples
(cherry picked from commit 0a0f5f1bbe4bf256a14dee0ab2af3065a251a72c)
|
| |
|
|
|
|
| |
This note will automatically cause the bug entry to be closed as fixed when
the next package (including this change) is uploaded.
(cherry picked from commit 04b9ffa56f54976f6a3324a3673915a036646ea6)
|
| |
|
|
| |
There was a leftover override, installing it into the wrong package.
|
