From: "Amadeusz Żołnowski" <aidecoe@aidecoe.name>
To: notmuch@notmuchmail.org
Subject: Re: muchsync files renames
Date: Sun, 23 Aug 2015 09:44:14 +0100 [thread overview]
Message-ID: <871teu8kdd.fsf@freja.aidecoe.name> (raw)
In-Reply-To: <876146o920.fsf@ta.scs.stanford.edu>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
Hi David,
Fist of all thank you for such elaborate answer.
I have missed the paragraph about maildir.synchronize_flags somehow. I
have it enabled. So this must be source of a problem (?).
Here follows steps I followed:
1. I initialized server locally with muchsync -vv. My mail is stored in
~/Mail on the server.
2. I run muchsync --init ~/mail SERVER. (Directory names do not need to
be the same, do they?)
3. I run muchsync SERVER.
4. When it lasted much longer then initialization I canceled it by
single SIGINT (^c).
5. I rerun muchsync SERVER and then it notified me that notmuch
identified files names changes - more than 1000.
6. I waited a bit and then I canceled it by SIGINT.
7. I run muchsync --noup SERVER. This took only seconds to finish.
I suspected that muchsync at step 3 and 5 tried to push files renames
back to server. But now I am not sure what was going on. Have I
desynchronized file mail flags? It's hard to say if anything has broken
for me, but I am a bit worried anyway.
If I just disable maildir.synchronize_flags and rerun muchsync, will
everything get synchronized properly?
--
Amadeusz Żołnowski
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 950 bytes --]
next prev parent reply other threads:[~2015-08-23 8:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 21:02 muchsync files renames Amadeusz Żołnowski
2015-08-23 5:41 ` David Mazieres
2015-08-23 8:44 ` Amadeusz Żołnowski [this message]
2015-08-23 20:06 ` David Mazieres
2015-08-23 20:43 ` David Mazieres
2015-08-24 22:14 ` Amadeusz Żołnowski
2015-08-26 6:31 ` Amadeusz Żołnowski
[not found] ` <87vbbwnbb4.fsf@freja.aidecoe.name>
[not found] ` <87io7wr50y.fsf@ta.scs.stanford.edu>
2015-08-31 11:59 ` Amadeusz Żołnowski
2015-08-31 17:27 ` dm-list-email-notmuch
2015-08-31 22:11 ` Amadeusz Żołnowski
2015-08-31 23:43 ` David Mazieres
2015-09-01 22:52 ` Amadeusz Żołnowski
2015-09-01 23:20 ` synchronize_flags leaving files in new (was muchsync files renames) dm-list-email-notmuch
2015-09-02 21:01 ` Amadeusz Żołnowski
2015-09-02 0:37 ` muchsync files renames David Bremner
2015-09-02 0:46 ` dm-list-email-notmuch
2015-09-02 21:21 ` Amadeusz Żołnowski
2015-09-02 23:05 ` David Bremner
2015-09-09 17:49 ` Amadeusz Żołnowski
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=871teu8kdd.fsf@freja.aidecoe.name \
--to=aidecoe@aidecoe.name \
--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).