mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-25 12:28:09 +01:00
NEWS: News for big endian sha1 bug fix.
We could give more details about how to migrate tags, but I'm not sure that it's a practical problem, or just a theoretical one.
This commit is contained in:
parent
20adfe39d7
commit
7f07bfd6d0
1 changed files with 17 additions and 1 deletions
18
NEWS
18
NEWS
|
@ -1,6 +1,22 @@
|
||||||
Notmuch 0.17~rc1 (2013-11-20)
|
Notmuch 0.17~rc2 (2013-xx-yy)
|
||||||
=============================
|
=============================
|
||||||
|
|
||||||
|
Incompatible change in SHA1 computation
|
||||||
|
---------------------------------------
|
||||||
|
|
||||||
|
Previously on big endian architectures like sparc and powerpc the
|
||||||
|
computation of SHA1 hashes was incorrect. This meant that messages
|
||||||
|
with overlong or missing message-ids were given different computed
|
||||||
|
message-ids than on more common little endian architectures like i386
|
||||||
|
and amd64. If you use notmuch on a big endian architecture, you are
|
||||||
|
strongly advised to make a backup of your tags using `notmuch dump`
|
||||||
|
before this upgrade. You can locate the affected files using something
|
||||||
|
like:
|
||||||
|
|
||||||
|
notmuch dump | \
|
||||||
|
awk '/^notmuch-sha1-[0-9a-f]{40} / \
|
||||||
|
{system("notmuch search --exclude=false --output=files id:" $1)}'
|
||||||
|
|
||||||
Command-Line Interface
|
Command-Line Interface
|
||||||
----------------------
|
----------------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue