Re: WARNING: database upgrade coming
authorJani Nikula <jani@nikula.org>
Mon, 17 Mar 2014 19:12:26 +0000 (21:12 +0200)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 18:00:48 +0000 (10:00 -0800)
8e/4feabd9379445248510f6d6edbbdfef9feaa58 [new file with mode: 0644]

diff --git a/8e/4feabd9379445248510f6d6edbbdfef9feaa58 b/8e/4feabd9379445248510f6d6edbbdfef9feaa58
new file mode 100644 (file)
index 0000000..30ce37d
--- /dev/null
@@ -0,0 +1,96 @@
+Return-Path: <jani@nikula.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 12A04431FBF\r
+       for <notmuch@notmuchmail.org>; Mon, 17 Mar 2014 12:12:40 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id LTbycXsOVQgg for <notmuch@notmuchmail.org>;\r
+       Mon, 17 Mar 2014 12:12:32 -0700 (PDT)\r
+Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com\r
+ [74.125.83.54])       (using TLSv1 with cipher RC4-SHA (128/128 bits))        (No client\r
+ certificate requested)        by olra.theworths.org (Postfix) with ESMTPS id\r
+ 525DC431FBD   for <notmuch@notmuchmail.org>; Mon, 17 Mar 2014 12:12:32 -0700\r
+ (PDT)\r
+Received: by mail-ee0-f54.google.com with SMTP id d49so4505175eek.13\r
+       for <notmuch@notmuchmail.org>; Mon, 17 Mar 2014 12:12:29 -0700 (PDT)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=1e100.net; s=20130820;\r
+       h=x-gm-message-state:from:to:subject:in-reply-to:references\r
+       :user-agent:date:message-id:mime-version:content-type;\r
+       bh=jpGqplDgPl7limnPoAbmUcUogO5uMetjcO4bjBW+Ols=;\r
+       b=h8U5A4j0IO04MJRNXATBnte5++qEGfcpkENw6f9wCLGmTXXybszkez+J85shdAMqg6\r
+       u8cRPWf6FhqiVflv7ngvWva9cEpeEdOrmL559nlhzDh3HDkC17LVN8DtSHlfVS+fI6y4\r
+       omJarL/zWtxxxHnYTWAz0ESLBt1qZ/WF0TSu0tKMqNN1cnr8MF5zlI98aRQrJxvAR6ls\r
+       sq9lr4DYC/4ElykwLRjvqpX7MTgelloOCq2iIV0ke8Sd1cTLqUgdb+pyHwV6gwyWpmDK\r
+       E2kq4n09t7Bct5l+UjH2rrXbYosU/aMf37t8QbefQi3ybVzKL6WZEs+8dLBt87PyC1wG\r
+       C2CQ==\r
+X-Gm-Message-State:\r
+ ALoCoQlROT7nsxxyHAHRFFl0u0XELyQgTuqlpzFZbP7+JZVg8+ON3zcy62qlxHhn5CmQsn+lcm9v\r
+X-Received: by 10.14.106.193 with SMTP id m41mr9724281eeg.62.1395083549553;\r
+       Mon, 17 Mar 2014 12:12:29 -0700 (PDT)\r
+Received: from localhost (dsl-hkibrasgw2-58c36f-91.dhcp.inet.fi.\r
+       [88.195.111.91])\r
+       by mx.google.com with ESMTPSA id g3sm29133167eet.35.2014.03.17.12.12.27\r
+       for <multiple recipients>\r
+       (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+       Mon, 17 Mar 2014 12:12:28 -0700 (PDT)\r
+From: Jani Nikula <jani@nikula.org>\r
+To: Jameson Graef Rollins <jrollins@finestructure.net>,\r
+       David Bremner <david@tethera.net>, Notmuch list <notmuch@notmuchmail.org>\r
+Subject: Re: WARNING: database upgrade coming\r
+In-Reply-To: <87txawkam3.fsf@servo.finestructure.net>\r
+References: <874n37a017.fsf@zancas.localnet>\r
+       <87txawkam3.fsf@servo.finestructure.net>\r
+User-Agent: Notmuch/0.17+142~g30045abd801f (http://notmuchmail.org)\r
+       Emacs/24.3.1 (x86_64-pc-linux-gnu)\r
+Date: Mon, 17 Mar 2014 21:12:26 +0200\r
+Message-ID: <87a9cood0l.fsf@nikula.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 17 Mar 2014 19:12:40 -0000\r
+\r
+\r
+Hi Jamie -\r
+\r
+On Mon, 17 Mar 2014, Jameson Graef Rollins <jrollins@finestructure.net> wrote:\r
+> Hey, David et. al.  I recently did an upgrade to notmuch/master after\r
+> being out of the loop for a while and not noticing that a database\r
+> upgrade was pending.  The next notmuch new informed me that a database\r
+> upgrade was required, but it went ahead and did the upgrade unprompted.\r
+> Things went fine, but it did worry me a bit that I didn't know an\r
+> upgrade was pending and didn't have a chance to do a backup before it\r
+> happened.\r
+\r
+FWIW it should always be safe to interrupt the upgrade; I know we don't\r
+inform the user about this.\r
+\r
+> It would be nice if notmuch new would prompt users when an database\r
+> upgrade is pending, to give the user an option to abort before\r
+> proceeding so that they can do a backup if they'd like.\r
+\r
+Please see id:87lhy4f6pr.fsf@nikula.org for a summary on some of the\r
+pros and cons that have been discussed about prompting the user.\r
+\r
+\r
+BR,\r
+Jani.\r