From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id UC7OCKn4l2BDDQAAgWs5BA (envelope-from ) for ; Sun, 09 May 2021 16:58:49 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id IMZRBKn4l2ALdAAAbx9fmQ (envelope-from ) for ; Sun, 09 May 2021 14:58:49 +0000 Received: from mail.notmuchmail.org (nmbug.tethera.net [144.217.243.247]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id C2304FFED for ; Sun, 9 May 2021 16:58:48 +0200 (CEST) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 2B10C27176; Sun, 9 May 2021 10:58:44 -0400 (EDT) Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) by mail.notmuchmail.org (Postfix) with ESMTPS id E5A5E2716D for ; Sun, 9 May 2021 10:58:40 -0400 (EDT) Received: by mail-pl1-x62d.google.com with SMTP id n16so7902248plf.7 for ; Sun, 09 May 2021 07:58:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:user-agent:mime-version; bh=S8G3dLrqeWbpzPt7tMiuccyGhgCZxn3qEvmDx6KHwoc=; b=GjQLZBcSK0vmXQssYqALDbR4mYJMqhnpAjg8Fs0bYSMP5IVl0UOH6kOmZRjNoIUyqF c3Uwg+w0QYnNKaqLq6ZVFYUOzmwA3jrA5Y5DvFEiH8hbDvWqWKVtcEp9H32nkAL6QdHi oF0lXx527R0dTo7RNgKPkEjchMw1p+N6QkUFUq7pl73418veL1qwV7IjCcSDcfRR/p0l 822pBJUxXSam4eP39n8qYkyWxOInu0j6+L6YTdc/Va2H1iw5hafThjUZrk3sBgyu7pka A8Tl8fbjuZrgfbDSz11+G+WUh3Qk65cnGwO/HfQR7g/1dGxEgca/3p/wbLIBW/9Bgf7A MQ3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:user-agent :mime-version; bh=S8G3dLrqeWbpzPt7tMiuccyGhgCZxn3qEvmDx6KHwoc=; b=A3qqt3bEMS+Q71I0QS2dqmMBtcC8Rb8hKYSPFxtaaxs9RrDCmiCHS1PGoLVGFG5wr+ spGvRt+Y6m8B1xErtqll0BArUWCTYba3eF9vdft6zr1dHiBwMAJbEGSvGehDFl6YUHq1 6PntzKrGabtNziuPYE2aasQryYFIbDbnUh2bHapMtsYfKy7LgtxwOOhcRpkqRoyz99/6 KbbyClHfHWxc2ikVhXIbWkhoZRcWCuaaSdoyGO00M+QNdmzJpR5hzIhOC7zs0PJRd0en 2XJHhdmCC6qGzcqloWm5Vthaxa10uoQyd3RyE3RPuPysK9tee5/ZgrrOA/Mx9mYCTB/r OEUQ== X-Gm-Message-State: AOAM530n4XlZm/M7/0VoRsdZB3uL6erE/ekcGd5/tHZzG2A00CxpW37k BO9p9A/2g1lc3TpsZK5mcU/p+R5h9jM= X-Google-Smtp-Source: ABdhPJw4TpnptIPzJTtp0lxqtDkOnmo3Sc9yZfUlZHb9V6M+j8T+9tELt6bGB3dihius63eYWUw+/g== X-Received: by 2002:a17:90b:1e4e:: with SMTP id pi14mr35685653pjb.120.1620572314438; Sun, 09 May 2021 07:58:34 -0700 (PDT) Received: from localhost ([198.27.182.161]) by smtp.gmail.com with ESMTPSA id v14sm5311459pgl.86.2021.05.09.07.58.33 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 09 May 2021 07:58:33 -0700 (PDT) From: Jack Kamm To: notmuch@notmuchmail.org Subject: Breakage after updating to 0.32 (database and path issues) Date: Sun, 09 May 2021 07:58:33 -0700 Message-ID: <87h7jcc5t2.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Message-ID-Hash: VFMRDWP7ROLOFPKV77T5REI7AZ5LZPXY X-Message-ID-Hash: VFMRDWP7ROLOFPKV77T5REI7AZ5LZPXY X-MailFrom: jackkamm@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.2.1 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1620572328; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=dn4stK3YoaJH4+hx8vG4qbwPYU2wEscMN9Twb5mLnU8=; b=pwpm88caFJ8+Bqup4I5tSf8aetCOyMFcWqhJ+Oh3NTgMR1Rmh6/xFgi18/8rrbiqQegtLt /F8ZTuMf1KHG+scqlpUxPmKm0s0WjFxsSs8tPQiy1KTcFcAq0OCKLrZjg9gDnDNsH22Dh+ +UbjWY7DG2SQ0XuLlohkxx+jvGJHwhrGj/b7iqBtIy/z2mKERppDq/7t6+5WNsCvk1sndz keJlnXIP14pyQI+gkwm3DPw59BivNUtvpUyTjIZCzIKKlWQ1Pf/Bw2iJqbYSiuxwy06azO BFMs5YwSAJcpL+Wv58t8gDkn9nJHxbgxkxRnD5TfNSn8jWVblKRR8/fzNJ1K9w== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1620572328; a=rsa-sha256; cv=none; b=RfHMarBEYDmodVCHUB1iecRc17u2xNhS3g4FnDoQsqnLlwKgK8xggD+uLIFXYe8obR0DLY 7PBxWZCyVv8njeOggGzhFdjkCq3hun6qWXEe2P1PqGu933UJwgwCuAHB20LnWff///r2xV JszMVNAzw19+Zjxy5InNq0tJnoN1490ZrW5rZ6KpLAHJVKEibKiH3jAHMgmNHiup0ehHXi 5ZWQqKEwD4sT2e61LOI+jhEGaI0uarzrBacoW+OxYav4BjqEwE5u3uEy402+dugNfEXti9 LSDRtLe45UkmKKjWsLbGfCrKnRm2n0muje+fX/SvLua42Apjuk82TBuW/w1mZw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=gmail.com header.s=20161025 header.b=GjQLZBcS; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 144.217.243.247 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Spam-Score: 0.52 Authentication-Results: aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=gmail.com header.s=20161025 header.b=GjQLZBcS; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 144.217.243.247 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Queue-Id: C2304FFED X-Spam-Score: 0.52 X-Migadu-Scanner: scn0.migadu.com X-TUID: /e63wTMjrlwf Updating to 0.32 broke my notmuch setup. notmuch could no longer find my database; after I changed some paths in my config, notmuch appeared to be able to find the database again, but wound up rebuilding it anyways, and could no longer find any of my emails. Any advice on fixing my setup would be appreciated. Also, I would suggest adding information to the v0.32 release notes of any breaking changes that were made, and how to migrate existing setups. I'm on Archlinux, and my email is located in $HOME/mail, with each of my accounts located under a different subfolder (e.g. $HOME/mail/gmail, $HOME/mail/work, etc). Below are details of the problems I ran into after updating to 0.32: First, notmuch could no longer find my database at $HOME/mail/.notmuch: > $ notmuch new > Error: Cannot open database at /home/jack/.local/share/notmuch/default: No such file or directory. According to the manpage of notmuch-config, I should be able to fix this by unsetting database.mail_root and leaving database.path to $HOME/mail: > database.path > Notmuch will store its database here, (in sub-directory named > .notmuch if database.mail_root is unset). > > Default: $MAILDIR variable if set, otherwise $HOME/mail. > > database.mail_root > 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. > > History: this configuration value was introduced in notmuch 0.32. > > Default: For compatibility with older configurations, the value of database.path is used if database.mail_root is unset. But contrary to the manpage this didn't fix the problem: > $ notmuch config set database.mail_root "" > $ notmuch new > Error: Cannot open database at /home/jack/.local/share/notmuch/default: No such file or directory. At this point I manually set database.path, but I got a new error this time: > $ notmuch config set database.path $HOME/mail/.notmuch > $ notmuch new > Warning: failed to open directory : No such file or directory > Found 0 total files (that's not much mail). > Error reading directory : No such file or directory > No new mail. > Note: A fatal error was encountered: Something went wrong trying to read or write a file Then I removed the setting for database.mail_root in my .notmuch-config, at which point "notmuch new" was able to run. However, it seems to have decided to rebuild the whole database, and now notmuch-show is not finding any emails. > notmuch new > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/flintlock > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/iamchert > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/position.DB > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/postlist.DB > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/record.DB > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/termlist.DB > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/postlist.baseB > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/position.baseA > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/termlist.baseB > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/record.baseB > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/postlist.baseA > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/position.baseB > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/termlist.baseA > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/xapian/record.baseA > Note: Ignoring non-mail file: /home/jack/mail/.notmuch/dump-20180526T233634.gz > Processed 15 total files in 18m 24s (0 files/sec.). > No new mail. Removed 884086 messages. Detected 12226 file renames. I'm also quite concerned about the "Removed 884086 messages." I'm guessing it only removed entries from the database, and doesn't seem to have deleted any files. But I need to double check my afew filters and mbsync configuration, to make sure no deletions propagate back to my remote. In the meantime I'm refraining from running mbsync/notmuch until I can verify that nothing will get deleted.