[PATCH 2/2] NEWS: News for big endian sha1 bug fix.

[Austin Clements]

Quoth david at tethera.net on Nov 24 at  5:29 pm:
> From: David Bremner 
> 
> 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.
> ---
>  NEWS | 14 +-
>  1 file changed, 13 insertions(+), 1 deletion(-)
> 
> diff --git a/NEWS b/NEWS
> index 3383ecf..31c6284 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -1,6 +1,18 @@
> -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. It should be possible to migrate the tags using a
> +script.
> +

Should this mention how to find such messages?  Something like

  notmuch dump |
  awk '/^notmuch-sha1-[0-9a-f]{40} / {system("notmuch search id:" $1)}'

[PATCH 2/2] NEWS: News for big endian sha1 bug fix.

[da...@tethera.net]

From: David Bremner 

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.
---
 NEWS | 14 +-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/NEWS b/NEWS
index 3383ecf..31c6284 100644
--- a/NEWS
+++ b/NEWS
@@ -1,6 +1,18 @@
-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. It should be possible to migrate the tags using a
+script.
+
 Command-Line Interface
 --

-- 
1.8.4.2

[PATCH 2/2] NEWS: News for big endian sha1 bug fix.

[david]

From: David Bremner da...@tethera.net

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.
---
 NEWS | 14 +-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/NEWS b/NEWS
index 3383ecf..31c6284 100644
--- a/NEWS
+++ b/NEWS
@@ -1,6 +1,18 @@
-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. It should be possible to migrate the tags using a
+script.
+
 Command-Line Interface
 --
 
-- 
1.8.4.2

___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: [PATCH 2/2] NEWS: News for big endian sha1 bug fix.

[Austin Clements]

Quoth da...@tethera.net on Nov 24 at  5:29 pm:
 From: David Bremner da...@tethera.net
 
 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.
 ---
  NEWS | 14 +-
  1 file changed, 13 insertions(+), 1 deletion(-)
 
 diff --git a/NEWS b/NEWS
 index 3383ecf..31c6284 100644
 --- a/NEWS
 +++ b/NEWS
 @@ -1,6 +1,18 @@
 -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. It should be possible to migrate the tags using a
 +script.
 +

Should this mention how to find such messages?  Something like

  notmuch dump |
  awk '/^notmuch-sha1-[0-9a-f]{40} / {system(notmuch search id: $1)}'
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch