From: "Miroslav Koškár" <mk@mkoskar.com>
To: notmuch@notmuchmail.org
Subject: database.path vs. database.mail_root: regression when relative
Date: Wed, 5 May 2021 17:56:48 +0200 [thread overview]
Message-ID: <20210505155648.pvaa3rbgrpp3a7rr@mkoskar.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1253 bytes --]
Consider following configuration in [database] section:
[database]
path=mail/main
With notmuch 0.32 running:
$ notmuch config list | grep database
database.backup_dir=/home/miro/mail/main/.notmuch/backups
database.hook_dir=/home/miro/mail/main/.notmuch/hooks
database.mail_root=mail/main
database.path=mail/main
It seem OK. Notice that backup_dir and hook_dir are absolute paths and
resolved correctly.
Running:
$ notmuch count
6454
All good!
Running:
$ notmuch new
...
Unexpected error with file mail/main/INBOX/cur/1615663870.253649_51.mirci,U=36739:2,S
add_file: Something went wrong trying to read or write a file
Error opening mail/main/INBOX/cur/1615663870.253649_51.mirci,U=36739:2,S: No such file or directory
...
Not good!
Setting database.path to an absolute path is a working workaround.
It seems that while notmuch can determine the correct location of the
database, when in need to access actual emails it fails. Coinciding with
the introduction of database.mail_root it seems that it's not
interpreted the same way when set (or "inherited" from database.path) as
relative value.
--
Miroslav Koškár
http://mkoskar.com/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2021-07-31 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 15:56 Miroslav Koškár [this message]
2021-08-02 11:31 ` database.path vs. database.mail_root: regression when relative David Bremner
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=20210505155648.pvaa3rbgrpp3a7rr@mkoskar.com \
--to=mk@mkoskar.com \
--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).