Re: Breakage after updating to 0.32 (database and path issues)

[Jack Kamm <jackkamm@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

David Bremner <david@tethera.net> writes:

> There is a bug related to relative values. Maybe that was what you encountered?
> There will be a point release soon with a fix for that bug. In the mean
> time you can just set database path to an absolute path.

Explicitly setting "database.path" to "/home/jack/mail" in my
".notmuch-config" indeed fixed the problem.

However previously, I simply had not set this variable at all in my
".notmuch-config", and "notmuch config get database.path" returned
"/home/jack/mail" (an absolute path).

So, I'm unsure if this was the underlying issue.

> You should not have to change your configuration to work with 0.32,
> other than temporarily making sure database.path has an absolute value.
> If you have a configuration file that works with 0.31 and not with 0.32,
> please share it as precisely as you can, including the contents of
> .notmuch-config. 

I've attached my .notmuch-config (slightly edited to remove some email addresses).

> That's correct. Notmuch does not delete mail files.

That's what I thought -- thanks for confirming this.


[-- Attachment #2: notmuch-config-for-bug-report.conf --]
[-- Type: text/plain, Size: 2897 bytes --]

# -*- mode: conf; -*-
# .notmuch-config - Configuration file for the notmuch mail system
#
# For more information about notmuch, see https://notmuchmail.org

# Database configuration
#
# The only value supported here is 'path' which should be the top-level
# directory where your mail currently exists and to where mail will be
# delivered in the future. Files should be individual email messages.
# Notmuch will store its database within a sub-directory of the path
# configured here named ".notmuch".
#

#[database]
#path=/home/jack/Maildir

# User configuration
#
# Here is where you can let notmuch know how you would like to be
# addressed. Valid settings are
#
#	name		Your full name.
#	primary_email	Your primary email address.
#	other_email	A list (separated by ';') of other email addresses
#			at which you receive email.
#
# Notmuch will use the various email addresses configured here when
# formatting replies. It will avoid including your own addresses in the
# recipient list of replies, and will set the From address based on the
# address to which the original email was addressed.
#

[user]
name=Jack Kamm
primary_email=jackkamm@gmail.com
other_email=xxx@xxx;xxx@xxx;xxx@xxx

# Configuration for "notmuch new"
#
# The following options are supported here:
#
#	tags	A list (separated by ';') of the tags that will be
#		added to all messages incorporated by "notmuch new".
#
#	ignore	A list (separated by ';') of file and directory names
#		that will not be searched for messages by "notmuch new".
#
#		NOTE: *Every* file/directory that goes by one of those
#		names will be ignored, independent of its depth/location
#		in the mail store.
#

[new]
tags=new;
ignore=.uidvalidity;.mbsyncstate

# Search configuration
#
# The following option is supported here:
#
#	exclude_tags
#		A ;-separated list of tags that will be excluded from
#		search results by default.  Using an excluded tag in a
#		query will override that exclusion.
#

[search]
exclude_tags=deleted;spam;

# Maildir compatibility configuration
#
# The following option is supported here:
#
#	synchronize_flags      Valid values are true and false.
#
#	If true, then the following maildir flags (in message filenames)
#	will be synchronized with the corresponding notmuch tags:
#
#		Flag	Tag
#		----	-------
#		D	draft
#		F	flagged
#		P	passed
#		R	replied
#		S	unread (added when 'S' flag is not present)
#
#	The "notmuch new" command will notice flag changes in filenames
#	and update tags, while the "notmuch tag" and "notmuch restore"
#	commands will notice tag changes and update flags in filenames
#

[maildir]
synchronize_flags=true

# Cryptography related configuration
#
# The following *deprecated* option is currently supported:
#
#	gpg_path
#		binary name or full path to invoke gpg.
#		NOTE: In a future build, this option will be ignored.
#		Setting $PATH is a better approach.
#

[crypto]
gpg_path=gpg

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]