1 |
On Sun, 2022-06-26 at 09:28 +0100, Matthew Smith wrote: |
2 |
> Add a news item explaining a maildir corruption bug in the mu/mu4e |
3 |
> mail reader. |
4 |
> --- |
5 |
> .../2022-06-06-mu-corruption.en.txt | 26 +++++++++++++++++++ |
6 |
> 1 file changed, 26 insertions(+) |
7 |
> create mode 100644 |
8 |
> 2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt |
9 |
> |
10 |
> diff --git a/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt |
11 |
> b/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt |
12 |
> new file mode 100644 |
13 |
> index 0000000..6603b5e |
14 |
> --- /dev/null |
15 |
> +++ b/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt |
16 |
> @@ -0,0 +1,26 @@ |
17 |
> +Title: Mu 1.7.23 Causing Maildir Corruption |
18 |
> +Author: Matthew Smith <matthew@g.o> |
19 |
> +Posted: 2022-06-26 |
20 |
> +Revision: 1 |
21 |
> +News-Item-Format: 2.0 |
22 |
> +Display-If-Installed: net-mail/mu-1.7.23 |
23 |
> + |
24 |
> +Development versions of mu between 1.7.18 and 1.7.25 have a bug causing |
25 |
> +mail file names to sometimes get mangled after moving messages between |
26 |
> +directories. Symptoms include unread messages never being marked as |
27 |
> +read. |
28 |
> + |
29 |
> +Users can check for corruption by checking to see if the following |
30 |
> +command produces any output: |
31 |
> + |
32 |
> + find ~/Maildir -name '*:2,*:*' |
33 |
> + |
34 |
> +Users can correct the corruption by running the following commands: |
35 |
> + |
36 |
> + find ~/Maildir -name '*:2,*:*' | |
37 |
> + sed "s/\(\([^:]*\)\(:2,\)\{1,\}\(:2,.*$\)\)/mv '\0' '\2\4'/" \ |
38 |
|
39 |
Would be nice to explain what the expression does in human way. Also, I |
40 |
think using `sed -E` would make this more readable. |
41 |
|
42 |
> + > rename.sh |
43 |
> + # review rename.sh |
44 |
> + sh rename.sh |
45 |
> + |
46 |
> +Upstream issue: https://github.com/djcb/mu/issues/2268 |
47 |
|
48 |
-- |
49 |
Best regards, |
50 |
Michał Górny |