Commit graph

15 commits

Author SHA1 Message Date
wiz
84222131a0 Bump depends pattern for dependency change from gmime24 to gmime. 2015-11-22 23:56:52 +00:00
wiz
d3a6b88b25 Update notmuch to 0.21:
Notmuch 0.21 (2015-10-29)
=========================

General
-------

Notmuch now requires gmime >= 2.6.7. The gmime 2.4 series is no longer
supported.

Database revision tracking: `lastmod:` queries

  Each message now has a metadata revision number that increases with
  every tagging operation. See the discussion of `lastmod:` in
  `notmuch-search-terms(7)` for more information.

Date queries now support `date:<expr>..!` shorthand for
`date:<expr>..<expr>`

  You can use, for example, `date:yesterday..!` to match from the
  beginning of yesterday to the end of yesterday. For further details,
  please refer to the `notmuch-search-terms` manual page.

Notmuch database upgrade to support `lastmod:` queries

  The above mentioned `lastmod:` prefix. This will be done
  automatically, without prompting on the next time `notmuch new` is
  run after the upgrade. The upgrade is not reversible, and the
  upgraded database will not be readable by older versions of
  Notmuch. As a safeguard, a database dump will be created in the
  `.notmuch` directory before upgrading.

Build System
------------

The ruby bindings are now built as part of the main notmuch build
process. This can be disabled with the `--without-ruby` option to
configure.

Building the documentation can be disabled with the `--without-docs`
option to configure.

Skipped individual tests are no longer considered as failures.

Command Line Interface
----------------------

Database revision tracking

  Two new options were added to support revision tracking. A global
  option "--uuid" (`notmuch(1)`) was added for to detect counter
  rollover and reinitialization, and `notmuch-count(1)` gained a
  `--lastmod` option to query database revision tracking data.

The `notmuch address` command supports new deduplication schemes

  `notmuch address` has gained a new `--deduplicate` option to specify
  how the results should be deduplicated, if at all. The alternatives
  are `no` (do not deduplicate, useful for processing the results with
  external tools), `mailbox` (deduplicate based on the full, case
  sensitive name and email address), and `address` (deduplicate based
  on the case insensitive address part). See the `notmuch-address`
  manual page for further information.

Emacs Interface
---------------

`notmuch-emacs-version` is used in `User-Agent` header

  The value of recently introduced variable `notmuch-emacs-version` is
  now used as a part of `User-Agent` header when sending emails.

Removed `notmuch-version` function by renaming it to `notmuch-cli-version`

  With existing variable `notmuch-emacs-version` the accompanied
  function which retrieves the version of `notmuch-command` is
  better named as `notmuch-cli-version`.

Query input now supports completion for "is:<tag>"

New message composition mode: `notmuch-compose-mode`

  This is mainly to fix fcc handling, but may be useful for user
  customization as well.

Allow filtering of search results in `notmuch-show`

Add function to rerun current tree-view search in search mode

Bug fix for replying to encrypted messages in `notmuch-tree` mode

Allow saved searched to specify tree view rather than search view

  Applies to saved searches run from `notmuch-hello`, or by a keyboard
  shortcut (`notmuch-jump`).  Can be set in the customize interface, or
  by adding :search-type tree to the appropriate saved search plist in
  `notmuch-saved-searches`.

Increase maximum size of rendered text parts

  The variable `notmuch-show-max-text-part-size` controls the maximum
  size (in bytes) which is automatically rendered. This may make
  rendering large threads slower. To get the previous behaviour set
  this variable to 10000.

Library
-------

The use of absolute paths is now enforced when calling
`notmuch_database_{open, create}`

New function `notmuch_directory_delete` to delete directory documents

  Previously there was no way to delete directory documents from the
  database, leading to confusing results when the "ghost" directory
  document of a renamed or deleted filesystem directory was
  encountered every time the parent directory was being scanned by
  `notmuch new`. The mtime of the old directory document was also used
  if a directory by the same name was added again in the filesystem,
  potentially bypassing the scan for the directory. The issues are
  fixed by providing a library call to delete directory documents, and
  deleting the old documents in `notmuch new` on filesystem directory
  removal or rename.

Database revision tracking

  Revision tracking is supported via a new prefix "lastmod:" in the
  query parser and the new function
  `notmuch_database_get_revision`. For the latter, see `notmuch(3)`.

New status code returning API for n_query_count_{messages,threads}

Deprecated functions

  `notmuch_query_search_threads`, `notmuch_query_search_messages`,
  `notmuch_query_count_messages`, and `notmuch_query_count_threads`
  are all deprecated as of this release.  Clients are encouraged to
  transition to the `_st` variants supporting better error reporting.

nmbug-status
------------

`nmbug-status` now supports specifying the sort order for each view.
2015-11-22 23:55:33 +00:00
agc
ddbf6ddecd Add SHA512 digests for distfiles for mail category
Problems found locating distfiles:
	Package mutt: missing distfile patch-1.5.24.rr.compressed.gz
	Package p5-Email-Valid: missing distfile Email-Valid-1.198.tar.gz
	Package pine: missing distfile fancy.patch.gz
	Package postgrey: missing distfile targrey-0.31-postgrey-1.34.patch
	Package qmail: missing distfile badrcptto.patch
	Package qmail: missing distfile outgoingip.patch
	Package qmail: missing distfile qmail-1.03-realrcptto-2006.12.10.patch
	Package qmail: missing distfile qmail-smtpd-viruscan-1.3.patch
	Package thunderbird24: missing distfile enigmail-1.7.2.tar.gz
	Package thunderbird31: missing distfile enigmail-1.7.2.tar.gz

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.
2015-11-03 23:27:00 +00:00
wiz
6842ad3d5d Update to 0.20.2:
Notmuch 0.20.2 (2015-06-27)
===========================

Emacs Interface
---------------

Bug fix for marking messages read in `notmuch-tree` mode.

Notmuch 0.20.1 (2015-06-01)
===========================

Test Suite
----------

Work around apparent gdb bug on arm64

Notmuch 0.20 (2015-05-31)
=========================

Command-Line Interface
----------------------

There is a new `mimetype:` search prefix

  The new `mimetype:` search prefix allows searching for the
  content-type of attachments, which is now indexed. See the
  `notmuch-search-terms` manual page for details.

Path to gpg is now configurable

  On systems with multiple versions of gpg, you can tell
  notmuch which one to use by setting `crypto.gpg_path`

Emacs
-----

Avoid rendering large text attachements.

Improved rendering of CID references in HTML.

Vim
---

Vim client now respects excluded tags.

Notmuch-Mutt
------------

Support messages without Message-IDs.

Library
-------

Undeprecate single message mboxes

  It seems more trouble to remove this feature than expected, so
  `notmuch new` will no longer nag about mboxes with a single message.

New error logging facility

  Clients should call `notmuch_database_status_string` to retrieve
  output formerly printed to stderr.

Several bug fixes related to stale iterators

New status code returning API for n_query_search_{messages,thread}

Fix for library `install_name` on Mac OS X

Fix for rounding of seconds

Documentation
-------------

Sphinx is now mandatory to build docs

  Support for using rst2man in place of sphinx to build the
  docmumentation has been removed.

Improved notmuch-search-terms.7

  The man page `notmuch-search-terms(7)` has been extended, merging
  some material from the relicensed wiki.

Contrib
-------

`notmuch-deliver` is removed. As far as we know, all functionality
previously provided by `notmuch-deliver` should now be provided by
`notmuch insert`, provided by the main notmuch binary.

nmbug-status
------------

`nmbug-status` now only matches local branches when reading
`status-config.json` from the `config` branch of the `NMBGIT`
repository.  To help new users running `nmbug-status`, `nmbug clone`
now creates a local `config` branch tracking `origin/config`.  Folks
who use `nmbug-status` with an in-Git config (i.e. you don't use the
`--config` option) who already have `NMBGIT` set up are encouraged to
run:

    git checkout config origin/config

in their `NMBGIT` repository (usually `~/.nmbug`).
2015-08-26 13:33:36 +00:00
wiz
fd434cbb0d Fix build with versioned py-docutils, and depend on 0.12.
From markd.
2015-02-26 12:17:04 +00:00
joerg
21e0ea169f Add forgotten patches to allow zlib 1.2.3 and rename libutil to
libmyutil.
2014-12-18 12:26:51 +00:00
joerg
9a14aa35dc Avoid confusion with libutil. Allow zlib 1.2.3. Bump revision. 2014-12-18 10:52:58 +00:00
wiz
a09e3f9644 Recursive PKGREVISION bump for notmuch shlib major change. 2014-11-19 13:06:46 +00:00
wiz
f8b0924727 Update to 0.19:
Notmuch 0.19 (2014-11-14)
=========================

Overview
--------

This release improves the reliability of `notmuch dump` and the error
handling for `notmuch insert`. The new `notmuch address` command is
intended to make searching for email addresses more convenient. At the
library level the revised handling of missing messages fixes at least
one bug in threading. The release also includes several interface
improvements to the emacs interface, most notably the ability to bind
keyboard shortcuts to saved searches.

Command-Line Interface
----------------------

Stopped `notmuch dump` failing if someone writes to the database

  The dump command now takes the write lock when running. This
  prevents other processes from writing to the database during the
  dump which would cause the dump to fail. Note, if another notmuch
  process already has the write lock the dump will not start, so
  script callers should still check the return value.

`notmuch insert` requires succesful message indexing for success status

  Previously the `notmuch insert` subcommand indicated success even if
  the message indexing failed, as long as the message was delivered to
  file system. This could have lead to delivered messages missing
  tags, etc. `notmuch insert` is now more strict, also requiring
  succesful indexing for success status. Use the new `--keep` option
  to revert to the old behaviour (keeping the delivered message file
  and returning success even if indexing fails).

`notmuch insert` has gained support for `post-insert` hook

  The new `post-insert` hook is run after message delivery, similar to
  `post-new`. There's also a new option `notmuch insert --no-hooks` to
  skip the hook. See the notmuch-hooks(1) man page for details.

`notmuch deliver` is deprecated

  With this release we believe that `notmuch insert` has reached
  parity with `notmuch deliver`. We recommend that all users of
  `notmuch deliver` switch to `notmuch insert` as the former is
  currently unmaintained.

`notmuch search` now supports `--duplicate=N` option with `--output=messages`

  Complementing the `notmuch search --duplicate=N --output=files`
  options, the new `--duplicate=N --output=messages` combination
  limits output of message IDs to messages matching search terms that
  have at least `N` files associated with them.

Added `notmuch address` subcommand

  This new subcommand searches for messages matching the given search
  terms, and prints the addresses from them. Duplicate addresses are
  filtered out. The `--output` option controls which of the following
  information is printed: sender addresses, recipient addresses and
  count of duplicate addresses.

Emacs Interface
---------------

Use the `j` key to access saved searches from anywhere in notmuch

  `j` is now globally bound to `notmuch-jump`, which provides fast,
  interactive keyboard shortcuts to saved searches.  For example,
  with the default saved searches `j i` from anywhere in notmuch will
  bring up the inbox.

Improved handling of the unread tag

  Notmuch now marks an open message read (i.e., removes the unread
  tag) if point enters the message at any time in a show buffer
  regardless of how point got there (mouse click, cursor command, page
  up/down, notmuch commands such as n,N etc). This fixes various
  anomalies or bugs in the previous handling. Additionally it is
  possible to customize the mark read handling by setting
  `notmuch-show-mark-read-function` to a custom function.

Expanded default saved search settings

  The default saved searches now include several more common searches,
  as well as shortcut keys for `notmuch-jump`.

Improved `q` binding in notmuch buffers

  `q` will now bury rather than kill a notmuch search, show or tree
  buffer if there are multiple windows showing the buffer. If only a
  single window is showing the buffer, it is killed.

`notmuch-show-stash-mlarchive-link-alist` now supports functions

  Some list archives may use a more complicated scheme for referring
  to messages than just concatenated URL and message ID. For example,
  patchwork requires a query to translate message ID to a patchwork
  patch ID. `notmuch-show-stash-mlarchive-link-alist` now supports
  functions to better cover such cases. See the help documentation for
  the variable for details.

Library changes
---------------

Introduced database version 3 with support for "database features."

  Features are independent aspects of the database schema.
  Representing these independently of the database version number will
  let us evolve the database format faster and more incrementally,
  while maintaining better forwards and backwards compatibility.

Library users are no longer required to call `notmuch_database_upgrade`

  Previously, library users were required to call
  `notmuch_database_needs_upgrade` and `notmuch_database_upgrade`
  before using a writable database.  Even the CLI didn't get this
  right, and it is no longer required.  Now, individual APIs may
  return `NOTMUCH_STATUS_UPGRADE_REQUIRED` if the database format is
  too out of date for that API.

Library users can now abort an atomic section by closing the database

  Previously there was no supported way to abort an atomic section.
  Callers can now simply close the database, and any outstanding
  atomic section will be aborted.

Add return status to notmuch_database_close and
notmuch_database_destroy

Bug fixes and performance improvements for thread linking

  The database now represents missing-but-referenced messages ("ghost
  messages") similarly to how it represents regular messages.  This
  enables an improved thread linking algorithm that performs better
  and fixes a bug that sometimes prevented notmuch from linking
  messages into the same thread.

nmbug
-----

The Perl script has been translated to Python; you'll need Python 2.7
or anything from the 3.x line.  Most of the user-facing interface is
the same, but `nmbug help` is not `nmbug --help`, and the following nmbug
commands have slightly different interfaces: `archive`, `commit`,
`fetch`, `log`, `pull`, `push`, and `status`.  For details on the
new interface for a given command, run `nmbug COMMAND --help`.

nmbug-status
------------

`nmbug-status` can now optionally load header and footer templates
from the config file.  Use something like:

    {
      "meta": {
        "header": "<!DOCTYPE html>\n<html lang="en">\n...",
        "footer": "</body></html>",
         ...
      },
      ...
    },

Python Bindings
---------------

Add support for `notmuch_query_add_tag_exclude`

Build System
------------

The notmuch binaries and libraries are now build with debugging symbols
by default.  Users concerned with disk space should change the
defaults when configuring or use the strip(1) command.
2014-11-19 13:06:14 +00:00
wiz
11d7195f65 Update to 0.18.2:
Notmuch 0.18.2 (2014-10-25)
===========================

Test Suite
----------

Translate T380-atomicity to use gdb/python

  The new version is compatible with gdb 7.8

Emacs 24.4 related bug fixes

  The Messages buffer became read-only, and the generated mime
  structure for signatures changed slightly.

Simplify T360-symbol-hiding

   Replace the use of `objdump` on the object files with `nm` on the
   resulting lib.
2014-10-27 08:35:59 +00:00
wiz
68c9960d7c Fix install_name on OS X. From J. Lewis Muir on pkgsrc-users.
Bump PKGREVISION since the binary package changes on OS X.
While here, add comments to all patches.
2014-09-01 08:14:07 +00:00
jperkin
78a122933c Fix build on SunOS. 2014-08-21 08:25:42 +00:00
wiz
0e2ee5f5db Disable emacs detection by default.
Add notmuch emacs option that pulls in emacs and installs compiled lisp
files as well.

Based on a similar patch by J. Lewis Muir on pkgsrc-users.

Bump PKGREVISION.
2014-08-17 10:45:05 +00:00
wiz
494248ec1d Update to 0.18.1:
Notmuch 0.18.1 (2014-06-25)
===========================

This is a bug fix and portability release.

Build System
------------

Add a workaround for systems without zlib.pc

Make emacs install robust against the non-existence of emacs

Put notmuch lib directory first in RPATH

Fix handling of html_static_path in sphinx

  Both the python bindings and the main docs had spurious settings of
  this variable.

Test Suite
----------

Use --quick when starting emacs

  This avoids a hang in the T160-json tests.

Allow pending break points in atomicity script

  This allows the atomicity tests to run on several more architectures/OSes.

Command-Line Interface
----------------------

To improve portability use fsync instead of fdatasync in
`notmuch-dump`. There should be no functional difference.

Library changes
---------------

Resurrect support for single-message mbox files

  The removal introduced a bug with previously indexed single-message
  mboxes.  This support remains deprecated.

Fix for phrase indexing

  There were several bugs where words intermingled from different
  headers and MIME parts could match a single phrase query.  This fix
  will affect only newly indexed messages.

Emacs Interface
---------------

Make sure tagging on an empty query is harmless

  Previously tagging an empty query could lead to tags being
  unintentionally removed.

Notmuch 0.18 (2014-05-06)
=========================

Overview
--------

This new release includes some enhancements to searching for messages
by filesystem location (`folder:` and `path:` prefixes under *General*
below).  Saved searches in *Emacs* have also been enhanced to allow
distinct search orders for each one.  Another enhancement to the
*Emacs* interface is that replies to encrypted messages are now
encrypted, reducing the risk of unintentional information disclosure.
The default dump output format has changed to the more robust
`batch-tag` format. The previously deprecated parsing of single
message mboxes has been removed. For detailed release notes, see
below.

General
-------

The `folder:` search prefix now requires an exact match

  The `folder:` prefix has been changed to search for email messages
  by the exact, case sensitive maildir or MH folder name. Wildcard
  matching (`folder:foo*`) is no longer supported. The new behaviour
  allows for more accurate mail folder based searches, makes it
  possible to search for messages in the top-level folder, and should
  lead to less surprising results than the old behaviour. Users are
  advised to see the `notmuch-search-terms` manual page for details,
  and review how the change affects their existing `folder:` searches.

There is a new `path:` search prefix.

  The new `path:` search prefix complements the `folder:` prefix. The
  `path:` prefix searches for email messages that are in particular
  directories within the mail store, optionally recursively using a
  special syntax. See the `notmuch-search-terms` manual page for
  details.

Notmuch database upgrade due to `folder:` and `path:` changes

  The above mentioned changes to the `folder:` prefix and the addition
  of `path:` prefix require a Notmuch database upgrade. This will be
  done automatically, without prompting on the next time `notmuch new`
  is run after the upgrade. The upgrade is not reversible, and the
  upgraded database will not be readable by older versions of
  Notmuch. As a safeguard, a database dump will be created in the
  `.notmuch` directory before upgrading.

Library changes
---------------

Notmuch database upgrade

  The libnotmuch consumers are reminded to handle database upgrades
  properly, either by relying on running `notmuch new`, or checking
  `notmuch_database_needs_upgrade()` and calling
  `notmuch_database_upgrade()` as necessary. This has always been the
  case, but in practise there have been no database upgrades in any
  released version of Notmuch before now.

Support for indexing mbox files has been dropped

  There has never been proper support for mbox files containing
  multiple messages, and the support for single-message mbox files has
  been deprecated since Notmuch 0.15. The support has now been
  dropped, and all mbox files will be rejected during indexing.

Message header parsing changes

  Notmuch previously had an internal parser for message headers. The
  parser has now been dropped in favour of letting GMime parse both
  the headers and the message MIME structure at the same pass. This is
  mostly an internal change, but the GMime parser is stricter in its
  interpretation of the headers. This may result in messages with
  slightly malformed message headers being now rejected.

Command-Line Interface
----------------------

`notmuch dump` now defaults to `batch-tag` format

  The old format is still available with `--format=sup`.

`notmuch new` has a --quiet option

  This option suppresses the progress and summary reports.

`notmuch insert` respects maildir.synchronize_flags config option

  Do not synchronize tags to maildir flags in `notmuch insert` if the
  user does not want it.

The commands set consistent exit status codes on failures

  The cli commands now consistently set exit status of 1 on failures,
  except where explicitly otherwise noted. The notable expections are
  the status codes for format version mismatches for commands that
  support formatted output.

Bug fix for checking configured new.tags for invalid tags

  `notmuch new` and `notmuch insert` now check the user configured
  new.tags for invalid tags, and refuse to apply them, similar to
  `notmuch tag`. Invalid tags are currently the empty string and tags
  starting with `-`.

Emacs Interface
---------------

Init file

  If the file pointed by new variable `notmuch-init-file` (typically
  `~/.emacs.d/notmuch-config.el`) exists, it is loaded at the end of
  `notmuch.el`. Users can put their personal notmuch emacs lisp based
  configuration/customization items there instead of filling
  `~/.emacs` with these.

Changed format for saved searches

  The format for `notmuch-saved-searches` has changed, but old style
  saved searches are still supported. The new style means that a saved
  search can store the desired sort order for the search, and it can
  store a separate query to use for generating the count notmuch
  shows.

  The variable is fully customizable and any configuration done
  through customize should *just work*, with the additional options
  mentioned above. For manual customization see the documentation for
  `notmuch-saved-searches`.

  IMPORTANT: a new style notmuch-saved-searches variable will break
  previous versions of notmuch-emacs (even search will not work); to
  fix remove the customization for notmuch-saved-searches.

  If you have a custom saved search sort function (not unsorted or
  alphabetical) then the sort function will need to be
  modified. Replacing (car saved-search) by (notmuch-saved-search-get
  saved-search :name) and (cdr saved-search) by
  (notmuch-saved-search-get saved-search :query) should be sufficient.

The keys of `notmuch-tag-formats` are now regexps

  Previously, the keys were literal strings.  Customized settings of
  `notmuch-tag-formats` will continue to work as before unless tags
  contain regexp special characters like `.` or `*`.

Changed tags are now shown in the buffer

  Previously tag changes made in a buffer were shown immediately. In
  some cases (particularly automatic tag changes like marking read)
  this made it hard to see what had happened (e.g., whether the
  message had been unread).

  The changes are now shown explicitly in the buffer: by default
  deleted tags are displayed with red strike-through and added tags
  are displayed underlined in green (inverse video is used for deleted
  tags if the terminal does not support strike-through).

  The variables `notmuch-tag-deleted-formats` and
  `notmuch-tag-added-formats`, which have the same syntax as
  `notmuch-tag-formats`, allow this to be customized.

  Setting `notmuch-tag-deleted-formats` to `'((".*" nil))` and
  `notmuch-tag-added-formats` to `'((".*" tag))` will give the old
  behavior of hiding deleted tags and showing added tags identically
  to tags already present.

Version variable

  The new, build-time generated variable `notmuch-emacs-version` is used
  to distinguish between notmuch cli and notmuch emacs versions.
  The function `notmuch-hello-versions` (bound to 'v' in notmuch-hello
  window) prints both notmuch cli and notmuch emacs versions in case
  these differ from each other.
  This is especially useful when using notmuch remotely.

Ido-completing-read initialization in Emacs 23

  `ido-completing-read` in Emacs 23 versions 1 through 3 freezes unless
  it is initialized. Defadvice-based *Ido* initialization is defined
  for these Emacs versions.

Bug fix for saved searches with newlines in them

  Split lines confuse `notmuch count --batch`, so we remove embedded
  newlines before calling notmuch count.

Bug fixes for sender identities

  Previously, Emacs would rewrite some sender identities in unexpected
  and undesirable ways.  Now it will use identities exactly as
  configured in `notmuch-identities`.

Replies to encrypted messages will be encrypted by default

  In the interest of maintaining confidentiality of communications,
  the Notmuch Emacs interface now automatically adds the mml tag to
  encrypt replies to encrypted messages. This should make it less
  likely to accidentally reply to encrypted messages in plain text.

Reply pushes mark before signature

  We push mark and set point on reply so that the user can easily cut
  the quoted text. The mark is now pushed before the signature, if
  any, instead of end of buffer so the signature is preserved.

Message piping uses the originating buffer's working directory

  `notmuch-show-pipe-message` now uses the originating buffer's
  current default directory instead of that of the `*notmuch-pipe*`
  buffer's.

nmbug
-----

nmbug adds a `clone` command for setting up the initial repository and
uses `@{upstream}` instead of `FETCH_HEAD` to track upstream changes.

  The `@{upstream}` change reduces ambiguity when fetching multiple
  branches, but requires existing users update their `NMBGIT`
  repository (usually `~/.nmbug`) to distinguish between local and
  remote-tracking branches.  The easiest way to do this is:

  1. If you have any purely local commits (i.e. they aren't in the
     nmbug repository on nmbug.tethera.net), push them to a remote
     repository.  We'll restore them from the backup in step 4.
  2. Remove your `NMBGIT` repository (e.g. `mv .nmbug .nmbug.bak`).
  3. Use the new `clone` command to create a fresh clone:

        nmbug clone http://nmbug.tethera.net/git/nmbug-tags.git

  4. If you had local commits in step 1, add a remote for that
     repository and fetch them into the new repository.
2014-07-03 15:01:46 +00:00
wiz
2595cf183e Import notmuch-0.17 as mail/notmuch, packaged for wip by myself
and tonnerre.

Notmuch is a system for indexing, searching, reading, and tagging
large collections of email messages in maildir or mh format. It uses
the Xapian library to provide fast, full-text search with a convenient
search syntax.
2014-01-09 12:15:23 +00:00